Zanie Blue

Note to self, should consider updating the following https://github.com/astral-sh/python-build-standalone/blob/4615f2f41cfb033f1838f1ca5f7e1f41d53e7222/cpython-unix/build.py#L840 https://github.com/astral-sh/python-build-standalone/blob/4615f2f41cfb033f1838f1ca5f7e1f41d53e7222/cpython-unix/build.py#L855 https://github.com/astral-sh/python-build-standalone/blob/4615f2f41cfb033f1838f1ca5f7e1f41d53e7222/cpython-unix/build.py#L510 https://github.com/astral-sh/python-build-standalone/blob/4615f2f41cfb033f1838f1ca5f7e1f41d53e7222/cpython-unix/build.py#L531 https://github.com/astral-sh/python-build-standalone/blob/4615f2f41cfb033f1838f1ca5f7e1f41d53e7222/cpython-unix/build.py#L877 Though I think we may want to retain the shared library even if `python` doesn't link to...

Agree on all those points. As a note, @geofft has been investigating some other problems that statically linking would solve. I expect he'll engage on exploring this further.

I think it's mostly related to downstream consumption requiring rpath hacks, like - https://github.com/PyO3/pyo3/pull/4890 - https://github.com/Nuitka/Nuitka/pull/3333

Thanks for sharing those @traversaro! That's helpful context. Just for some context on how I'm thinking about this pull request: I posted this for discussion and testing — I'm not...

We do use `--enable-optimizations` and Clang (for most builds) so the `-fno-semantic-interposition` case should be accounted for.

Superseded by #592

Thanks for the report!

Hi! Does `pyenv-virtualenv` not set `VIRTUAL_ENV`?

I'm not sure if we'll accept this functionality yet, but I think you'd want to add it at https://github.com/astral-sh/uv/blob/bf3286cd2d22f775107b807ac2e15d636bc334b7/crates/uv-python/src/discovery.rs#L225-L242

I see. The `.python-version` file shouldn't contain the name of an environment for use with uv — does pyenv support that?