Repository navigation
🐛 fix(discovery): search bare specs on PATH - #207
Merged
gaborbernat merged 3 commits intoNov 3, 2026
Merged
Conversation
Discovery probed an unparsed spec against the caller's working directory before PATH. A shared directory could supply the executable. Specs with a directory still take the explicit path branch.
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.
get_interpreter()probed an unrecognized bare spec against the caller's working directory before searchingPATH. A file in a shared working directory could replace the requested interpreter. Bare specs now use the executable-name search onPATH; explicit paths still resolve from their named directory. This addresses draft advisory ANT-2026-24EEPSBF.Bare spec resolution
PythonSpec.from_string_spec()stores an unrecognized string inspec.path. The old explicit branch then probed that value as a path. The branch now requires a directory component, leaving bare words for the existingPATHsearch.Behavior changes
A caller that intends a file in the working directory must write
./nameor another explicit relative path. A bare name can still match an executable onPATH. Absolute paths andtry_first_withretain their existing handling.Reported by Antigravity: ANT-2026-24EEPSBF.