Repository navigation
Conversation
Disambiguate the message shown when running 'uv python upgrade' with no uv-managed Python installations. Previously it said 'There are no installed versions to upgrade' which was confusing — it could mean either no Python was found at all, or everything is already up to date. Now it clearly states that no uv-managed installations were found and suggests using 'uv python install' first. Closes astral-sh#16783
Author
|
Hey everyone, I am very very sorry I got stuck in work-related stuff and haven't been able to follow up on this. I am happy if anyone else can take care of this from here or if the maintainers want to push the final bits. Apologies again for the delay! |
Member
|
Sorry, this is now fixed by #18353 |
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.
Closes #17182
When
--config-fileorUV_CONFIG_FILEis set, there's currently no indication in verbose output that a custom config file is being used (and that user-level/workspace config is being ignored). This can make debugging configuration issues pretty confusing.This adds a
tracing::debug!line that logs the resolved config file path and notes that user-level and workspace configuration is being skipped, so it shows up with-v:Follows the same pattern as the existing debug lines in
FilesystemOptions::user(),system(), andfrom_directory().