Charlie Marsh 53d1a7aa6e Always use base Python discovery logic for cached environments (#11254) ... ## Summary This is attempting to solve the same problem surfaced in #11208 and #11209. However, those PRs only worked for our own managed Pythons. In Gentoo, for example, they disable the managed Pythons, which led to failures in the test suite, because the "base Python" returned after creating a virtual environment would differ from the "base Python" that you get after _querying_ an existing virtual environment. The fix here is to apply our same base Python normalization and discovery logic, to non-standalone / non-managed Pythons. We continue to use `sys._base_executable` for such Pythons when creating the virtualenv, but when _caching_, we perform this second discovery step. Closes https://github.com/astral-sh/uv/issues/11237.		2025-02-05 15:47:56 -05:00
..
python	Use explicit _GLibCVersion tuple in uv-python crate (#11122)	2025-01-31 11:52:38 +01:00
src	Always use base Python discovery logic for cached environments (#11254)	2025-02-05 15:47:56 -05:00
Cargo.toml	Install and remove managed Python to and from the Windows Registry (PEP 514) (#10634)	2025-01-23 14:13:41 +00:00
download-metadata.json	Sync latest Python releases (#10637)	2025-01-15 12:55:31 -06:00
fetch-download-metadata.py	Update references to python-build-standalone to reflect the transferred project (#9977)	2024-12-17 20:19:58 +00:00
template-download-metadata.py	Update riscv64 Python downloads to allow install on riscv64gc (#10937)	2025-01-24 09:33:29 -06:00