-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Feature Request: Add a way to get tool venv specific information when using uv tool
#7311
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
Comments
I think this may be a We're adding suffix support (#7095) |
Thanks for sharing your use-cases! |
@zanieb Good to hear! Is |
Oh sorry no it doesn't exist but I think it should — I think it'd be a better experience for your use-cases than adding these flags to |
I would also like to see something like "show install command".
Being able to see this information across all installed tools at once would be really helpful. As a third option to the ones proposed in the original post, maybe there could be a
Or a fourth option of
|
Alternatively,
Related to #8028 where uv may not currently remember how a tool was installed |
I'm also replacing my pipx usage with UV and I was explicitly looking for UV's equivalent of FWIW I think @KyleKing 's suggestion of @zanieb 's since just the |
It would be very helpful to have the following additional functionality as flags for
uv tool list
:--show-full-dep-tree
: show all of the deps installed into the tool venvs.--show-tool-install-command
: show the original command used to install the tool (sometimes the package name does not match what is on pypi, e.g.p4python
installs theP4
package).To help differentiate tools installed with a more complicated setup, it is really helpful to have an additional suffix that gets appended to all installed script entry points (
pipx
does this via the--suffix
flag).Use case:
coverage
with additionalpytest
deps like this:uv tool install coverage --with pytest --with pytest-spec --with pytest-sugar
.uvx coverage run -m pytest
to run tests with my desired plugins on any project.The text was updated successfully, but these errors were encountered: