Conversation
| assert tester.status_code == 1 | ||
| assert ( | ||
| tester.io.fetch_error() | ||
| == "You cannot specify explicit `--extras` while installing `--all-extras`.\n" |
There was a problem hiding this comment.
I'm not sure about using --all-extras as words rather than treating it as a single token in this error message. I'd expect something like "You can't specify both --extras and --all-extras.".
|
Will |
No, that makes for a "magic" value which could break existing setups. |
If we really wanted to go that route, |
I'd avoid that too:
|
|
pre-commit.ci autofix |
|
Thanks for cleaning this up @neersighted. 👍 |
|
@neersighted @kroeschl any idea when this will be released? It isn't in 1.1.14 I see. |
This is in 1.2.0b2 and later, but it was never ported it back to 1.1.x. |
Co-authored-by: Bjorn Neergaard <[email protected]>
|
(in reply to a now deleted comment by @AiGeneratedUsername)
The addition of new features in Poetry proper does not relate to the implementation of new features in plugins. I don't think it's helpful or fair to say an accepted change that doesn't scratch your particular itch or do everything you would like to see is deficient in this situation. In any case, there is an open request on python-poetry/poetry-plugin-export#153 to implement the same feature in the plugin; please add your 👍 there. |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Add
--all-extrasflag toinstallcommandResolves: #3413
Add an
--all-extrasflag to theinstallcommand for projects which use multiple sets of extras. Update documentation for the new flag.