Skip to content
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

--no-system flag does not appear on the latest CLI help #9035

Closed
pesap opened this issue Nov 12, 2024 · 3 comments · Fixed by #9040
Closed

--no-system flag does not appear on the latest CLI help #9035

pesap opened this issue Nov 12, 2024 · 3 comments · Fixed by #9040
Assignees
Labels
bug Something isn't working

Comments

@pesap
Copy link

pesap commented Nov 12, 2024

I was reading through the documentation of uv pip install and found the --no-system flag here. However, the latest uv CLI help (from uv pip install does not appear to list it or describe it. Only --system appears on the help. I think it would nice to include it to the CLI help. Any thoughts?

My UV version

uv 0.5.1 (f399a52 2024-11-08)

@charliermarsh
Copy link
Member

We generally have negation flags with --no- for each boolean, but adding them to the CLI help would be too verbose.

@pesap
Copy link
Author

pesap commented Nov 12, 2024

Totally agree it would be to verbose to add the description for each boolean. I was wondering the rationale, since this flag does exist on CLI help of uv pip tree. Anywho, thanks for the amazing tool!

@charliermarsh
Copy link
Member

Ohh that might be a mistake on uv pip tree! Thanks!

charliermarsh added a commit that referenced this issue Nov 12, 2024
## Summary

This is hidden from all other commands, so it looks like an oversight.

Closes #9035.
@charliermarsh charliermarsh added the bug Something isn't working label Nov 12, 2024
@charliermarsh charliermarsh self-assigned this Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants