Improve reporting of managed interpreter symlinks in uv python list#18459
Merged
zanieb merged 9 commits intoastral-sh:mainfrom Mar 19, 2026
Merged
Improve reporting of managed interpreter symlinks in uv python list#18459zanieb merged 9 commits intoastral-sh:mainfrom
uv python list#18459zanieb merged 9 commits intoastral-sh:mainfrom
Conversation
When `--managed-python` is used, widen discovery to include search path sources so that symlinks pointing to managed installations are found, then post-filter to keep only managed interpreters. Previously, `OnlyManaged` only searched the `Managed` source, missing symlinks in `~/.local/bin/` and similar PATH directories that point to uv-managed Python installations. Fixes astral-sh#17959 https://claude.ai/code/session_01Q6Uo1r3YhrdCWyKPXB5X5R
Extend the post-filter to handle both directions: `--managed-python` keeps only managed interpreters, and `--no-managed-python` excludes managed interpreters (e.g., symlinks on the search path that point to uv-managed installations). https://claude.ai/code/session_01Q6Uo1r3YhrdCWyKPXB5X5R
The previous test used `with_versions_as_managed` which changes the discovery source to `Managed` — bypassing the search path symlink scenario. The new test uses `python install` to create real symlinks in `bin_dir`, then adds `bin_dir` to `UV_TEST_PYTHON_PATH` to verify that `--no-managed-python` correctly excludes symlinks pointing to managed installations, and `--managed-python` includes them. https://claude.ai/code/session_01Q6Uo1r3YhrdCWyKPXB5X5R
zanieb
commented
Mar 13, 2026
zanieb
commented
Mar 13, 2026
Merging this PR will degrade performance by 5.49%
Performance Changes
Comparing 
|
1 similar comment
Merging this PR will degrade performance by 5.49%
Performance Changes
Comparing
|
Gankra
approved these changes
Mar 19, 2026
Comment on lines
+173
to
+176
| .filter(|installation| match python_preference { | ||
| PythonPreference::OnlyManaged => installation.interpreter().is_managed(), | ||
| PythonPreference::OnlySystem => !installation.interpreter().is_managed(), | ||
| PythonPreference::Managed | PythonPreference::System => true, |
Contributor
There was a problem hiding this comment.
Can this just be python_preference.allows(installation.source)?
Member
Author
There was a problem hiding this comment.
No, here we want to check if the installation is managed regardless of the source, so we need to actually check where interpreter's base prefix is. It does seem like PythonPreference::allows_interpreter would be useful though.
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
3 participants
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.
Closes #17959
Expands discovery to always include a system scan even if
--managed-pythonis used to find links to managed interpreters on thePATH. Then filters reported interpreters by whether or not they are managed after discovery, so--no-managed-pythonwill never report those symlinks.