Zanie Blue 2966471db2 Prefer Python executable names that match the request over default names (#9066) ... This restores behavior previously removed in https://github.com/astral-sh/uv/pull/7649. I thought it'd be clearer (and simpler) to have a consistent Python executable name ordering. However, we've seen some cases where this can be surprising and, in combination with #8481, can result in incorrect behavior. For example, see https://github.com/astral-sh/uv/issues/9046 where we prefer `python3` over `python3.12` in the same directory even though `python3.12` was requested. While `python3` and `python3.12` both point to valid Python 3.12 environments there, the expectation is that when `python3.12` is requested that the `python3.12` executable is preferred. This expectation may be less obvious if the user requests `python@3.12`, but uv does not distinguish between these request forms. Similarly, this may be surprising as by default uv prefers `python` over `python3` but when requesting `python3.12` the preference will be swapped.		2024-11-13 10:00:23 -06:00
..
python	Use base executable to set virtualenv Python path (#8481)	2024-11-07 14:29:54 -06:00
src	Prefer Python executable names that match the request over default names (#9066)	2024-11-13 10:00:23 -06:00
Cargo.toml	Add support for installing versioned Python executables on Windows (#8663)	2024-10-31 15:58:35 +00:00
download-metadata.json	Fix a typo in fetch-download-metadata.py (#8515)	2024-10-24 07:33:14 -05:00
fetch-download-metadata.py	Fix a typo in fetch-download-metadata.py (#8515)	2024-10-24 07:33:14 -05:00
template-download-metadata.py	Add support for managed installs of free-threaded Python (#8100)	2024-10-14 15:18:52 -05:00