mirror of
https://github.com/astral-sh/uv.git
synced 2025-11-13 09:12:32 +00:00
2966471db2
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. |
||
|---|---|---|
| .. | ||
| python | ||
| src | ||
| Cargo.toml | ||
| download-metadata.json | ||
| fetch-download-metadata.py | ||
| template-download-metadata.py | ||