Charlie Marsh 2fad82c735 Set base executable when returning virtual environment (#11209) ... ## Summary I'm not sure that this has much of an effect in practice, but currently, when we return a virtual environment, the `sys_base_executable ` of the parent ends up being retained as `sys_base_executable` of the created environment. But these can be, like, subtly different? If you have a symlink to a Python, then for the symlink, `sys_base_executable` will be equal to `sys_executable`. But when you create a virtual environment for that interpreter, we'll set `home` to the resolved symlink, and so `sys_base_executable` will be the resolved symlink too, in general. Anyway, this means that we should now have a consistent value between (1) returning `Virtualenv` from the creation routine and (2) querying the created interpreter.		2025-02-04 22:32:47 +00:00
..
python	Use explicit _GLibCVersion tuple in uv-python crate (#11122)	2025-01-31 11:52:38 +01:00
src	Set base executable when returning virtual environment (#11209)	2025-02-04 22:32:47 +00: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