-
Notifications
You must be signed in to change notification settings - Fork 739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List installed tools when no command is provided to uv tool run
#5553
List installed tools when no command is provided to uv tool run
#5553
Conversation
9fa6661
to
91ff1c6
Compare
CI failures — seem unrelated to this change. |
From Charlie:
A tool can have multiple executables installed. |
Did I misunderstand the issue? I'm not sure I follow your point. |
91ff1c6
to
33aae6e
Compare
nvm, my bad. I didn't see the code and from title I thought it's going to list tool names only but not exposed entry points. |
----- stdout ----- | ||
black v24.2.0 | ||
- black | ||
- blackd | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't it also show a message about what the below list means:
Available tools and executables to run:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion! However, since I'm simply reusing the tool_list
, the output will exactly match uv run list
. Additionally, if we want to display a message, we would probably expect the output of uv run list
to change as well. I can make the change if desired, or perhaps it would be more suitable to make the change in a follow-up PR.
Summary
Part of #4024
Test Plan
Test cases included.