Skip to content

Log config file path in verbose output when --config-file is used - #18027

Closed
omair445 wants to merge 3 commits into
astral-sh:mainfrom
omair445:config-file-verbose-output
Closed

omair445 wants to merge 3 commits into
astral-sh:mainfrom
omair445:config-file-verbose-output

Conversation

@omair445

Copy link
Copy Markdown

Closes #17182

When --config-file or UV_CONFIG_FILE is 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:

DEBUG Using configuration file at `/path/to/uv.toml`; ignoring user-level and workspace configuration

Follows the same pattern as the existing debug lines in FilesystemOptions::user(), system(), and from_directory().

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
@omair445

Copy link
Copy Markdown
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!

@konstin

konstin commented Mar 11, 2026

Copy link
Copy Markdown
Member

Sorry, this is now fixed by #18353

@konstin konstin closed this Mar 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make usage of --config-file/UV_CONFIG_FILE visible in verbose output

2 participants