Show tool versions in uv tool list
#4653
Labels
cli
Related to the command line interface
good first issue
Good for newcomers
needs-design
Needs discussion, investigation, or design
preview
Experimental behavior
Comments
zanieb
added
needs-design
Closed
|
The cargo command which includes both the version and entrypoints could be used as an inspiration too. ❯ cargo install --list
sqlx-cli v0.7.3:
cargo-sqlx
sqlx |
|
Nice, I like the look of that |
|
I think the version should be showed by default because it doesn't add that much of information, the entrypoints maybe we should add a flag like |
|
Personally I'd probably do: Only because |
|
I don't love the pinned requirement syntax for something that will always be a specific version and isn't meant for consumption by another tool. |
|
I have created a pr based on @blueraft suggestion, lmk if it is the final design we want |
zanieb
added a commit
that referenced
this issue
Jul 3, 2024
<!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> Closes #4654 ## Summary The purpose of this is to show the entrypoints of each tool when running `uv tool list` as below: ``` $ uv tool list black black blackd ``` I used the proposed formatting as it was written in #4653 by @blueraft. I had to use spaces instead of tabs in order to make the test successful. Indeed in the test we are using a raw string and I did not manage to make the test pass when escaping the tab in the list.rs file so I used spaces everywhere. I had a deeper look into #4653 as well but it is more difficult as we need to get the version of the tool in the Tool object, I will continue on this next one later. Please tell me if anything else is needed I tried to follow the contribution guidelines but I might have forgotten something. Have a great day! ## Test Plan `cargo clippy` then by using the local version of uv as described in the Readme.md. ``` my-computer :~/mypath/uv$ cargo run -- tool list Compiling uv-cli v0.0.1 (/mypath/uv/crates/uv-cli) Compiling uv v0.2.18 (/mypath/uv/crates/uv) Finished `dev` profile [unoptimized + debuginfo] target(s) in 18.69s Running `target/debug/uv tool list` warning: `uv tool list` is experimental and may change without warning. black black blackd isort isort isort-identify-imports ``` and `cargo test tool_list` --------- Co-authored-by: Zanie Blue <[email protected]>
zanieb
added a commit
that referenced
this issue
Jul 3, 2024
<!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> Closes #4653 ## Summary Adds the tool version to the list command right beside the tool name ``` $ uv tool list black v24.2.0 ``` Following the proposed format discussed in #4653 ## Test Plan `cargo test tool_list` <!-- How was it tested? --> --------- Co-authored-by: Zanie Blue <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In addition to the name, it'd be nice to show the installed version. Should this be behind a flag? Are there other commands like
uv pip listorpipx listwe should take inspiration from?A simple example:
Related:
uv tool list#4654The text was updated successfully, but these errors were encountered: