Repository navigation
🐛 fix(tests): make interpreter fallback portable - #183
Merged
gaborbernat merged 2 commits intoNov 2, 2026
Merged
Conversation
gaborbernat
added
bug
gaborbernat
changed the title
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.
The free-threaded job and Python 3.9/3.10 jobs fail after the preferred path fallback change, blocking its validation. One check rejects a free-threaded build; another copies an interpreter that cannot find its standard library on those runners.
Discovery's preferred path checks now accept either build and use a controlled candidate at the interpreter interrogation boundary. They continue to exercise path replay and early stopping without requiring a relocated Python installation.