-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Running poetry --help
gives the behaviour of poetry list --help
instead of poetry list
#8710
Comments
Submit a merge request! |
I'll definitely give it a go if I have time - it's been added to my (exceedingly long) todo list |
Do you have some pointer on where to look in the code to know what part deals with the "--help"? Is it on the poetry source code? Or on the cleo source code? |
This is in Cleo repo and there is already python-poetry/cleo#249. It's non-trivial to tackle, but will be fixed in Cleo 3.0, which I am working on currently. |
This is in Cleo repo and there is already python-poetry/cleo#249. It's non-trivial to tackle, but will be fixed in Cleo 3.0, which I am working on currently. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option) and have included the output below.Issue
A common design for console applications is to give general help for using the command if the command is run with a
--help
flag. Some (including Poetry) also give this same output when running the command without arguments. Poetry (seemingly) accomplishes this by aliasingpoetry
to be equivalent topoetry list
.However, a confusing side effect of this is that running
poetry --help
is the equivalent topoetry list --help
. Given that users who runpoetry --help
likely want to learn about the available commands within Poetry, this behaviour is likely not the best design, since it creates additional work for users. Every time I forget the correct commands to use when working on a project with Poetry, I runpoetry --help
, only to need to remind myself of this behaviour and runpoetry
, which is a little frustrating.To be clear, this isn't a major issue, but I think that quality-of-life improvements such as this contribute significantly to the developer experience, so some attention to detail wouldn't go astray.
The text was updated successfully, but these errors were encountered: