Add test coverage for incorrect free-threaded Python version selection - #21124
Merged
zanieb merged 2 commits intoAug 14, 2026
Merged
zanieb merged 2 commits into
zanieb merged 2 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
zanieb
enabled auto-merge (squash)
August 14, 2026 03:26
EliteTK
added a commit
that referenced
this pull request
Aug 14, 2026
Python version ranges can encounter several version-specific executables in the same `PATH` directory, but filesystem enumeration does not establish which interpreters they actually launch. Preserve equal-priority fallback candidates through source filtering, query them in the existing installation pipeline, and reuse `PythonInstallationKey` ordering to prefer newer versions and default variants while preserving executable-name precedence, directory order, and lazy discovery. Follows #21124 --------- Co-authored-by: Zanie Blue <contact@zanie.dev> Co-authored-by: Tomasz (Tom) Kramkowski <tom@astral.sh>
VedantMadane
added a commit
to VedantMadane/uv
that referenced
this pull request
Sep 21, 2026
astral-sh#21124) Captures the behavior described in the Discord report where `requires-python = "==3.15.*"` selects a free-threaded interpreter when both variants are installed. The test contrasts deterministic managed-install discovery with selection through the installed executable aliases, which currently follows filesystem enumeration order. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>
VedantMadane
added a commit
to VedantMadane/uv
that referenced
this pull request
Sep 21, 2026
Python version ranges can encounter several version-specific executables in the same `PATH` directory, but filesystem enumeration does not establish which interpreters they actually launch. Preserve equal-priority fallback candidates through source filtering, query them in the existing installation pipeline, and reuse `PythonInstallationKey` ordering to prefer newer versions and default variants while preserving executable-name precedence, directory order, and lazy discovery. Follows astral-sh#21124 --------- Co-authored-by: Zanie Blue <contact@zanie.dev> Co-authored-by: Tomasz (Tom) Kramkowski <tom@astral.sh>
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Captures the behavior described in the Discord report where requires-python = "==3.15.*" selects a free-threaded interpreter when both variants are installed. The test contrasts deterministic managed-install discovery with selection through the installed executable aliases, which currently follows filesystem enumeration order.