messense

Can you create a minimal repro public repository? Your normal build log says it's using abi3 but the `PYO3_PRINT_CONFIG=1` output shows `abi3=false`.

> as well as getting this wrong by not supporting `pyenv-virtualenv` I'm using `pyenv-virtualenv` on macOS, I haven't encountered any issue.

> @stinodego Have you tried `pyenv activate`? It does set `VIRTUAL_ENV` in its code https://github.com/pyenv/pyenv-virtualenv/blob/017ea60cd35c8e20a659cc09498cd51bd3925035/bin/pyenv-sh-activate#L175-L178 My `pyenv shell` command also set `VIRTUAL_ENV` and `PYENV_VIRTUAL_ENV`. ```bash ~ ❯ pyenv shell test...

FYI, you can fake a virtualenv by setting the `VIRTUAL_ENV` env var if you know what you are doing: ```bash export VIRTUAL_ENV=$(python3 -c 'import sys; print(sys.base_prefix)') maturin develop ``` or...

BTW, there is a new [PEP 704](https://github.com/python/peps/pull/2964) pull request today that require virtual environments by default for installers (like pip).

I think it's possible, we can read `${dirname(maturin executable)}/../pyvenv.cfg` to see if maturin is installed in a venv and assume we're going to use that venv when no other venv...

@konstin This is because `cargo-xwin` does not keep debug libs by default, you can pass `--xwin-include-debug-libs` to keep them, or build in release mode instead. FYI, `msvcrtd.dll` is a "debug"-version...

Could be cmake detected wrong header paths, it's always a pain to cmake when doing cross compilation.

> plz merge, cross-compiling to windows doesn't work currently @sentialx we're still waiting for a new [`ureq`](https://github.com/algesten/ureq) 2.x release, consider asking `ureq` for a new release if you want to...

It's unlikely we will upgrade to a xwin version that uses reqwest, there is no point in pulling in two http client library in maturin, and we'd like to avoid...