Flag to install all extras

[l0b0]

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the documentation and believe that my question is not covered.

Feature Request

It would be handy to have a flag like --all-extras to install every package listed in any of the extras.

The specific use case is that I want the IDE to index the packages for every subsystem (AWS Lambda jobs in this case) for easier development.

Workarounds:

1. Creating a separate "extra" section with all the packages from all the other extras (example). This means duplication, which means it would be really easy for the sections to get out of sync.
2. Listing each extra specifically in the developer instructions.
3. This ugly code, used in anger here: poetry install --extras="$(sed --quiet '/\[tool\.poetry\.extras\]/,/^\[/{s/^\(.*\) = \[/\1/p}' pyproject.toml | sed --null-data 's/\n/ /g;s/ $//')" --remove-untracked

[sinoroc]

Related: #3369

[thclark]

Seconded for this one - I want to provide my team a vscode devcontainer that installs everything out of the box, and don't want to have to remember to update the .devcontainer file if we add extras to the library we're developing... so sounds like the same use case as the OP.

[abn]

Would supporting --extras . or --extras "*" as an alias for enabling all extras work here?

I am just curious if folks have a preference for --all-extras.

[l0b0]

--all-extras would be more explicit, and would avoid a) a special value or b) supporting any kind of regex, which would be another can of worms.

[kroeschl]

I don't have an opinion either way, but I'd like to use this feature to make dev testing somewhat easier. I posted a PR for --all-extras: #5452

[rjurney]

Any idea when this will be released?

[ecs-jnguyen]

It looks like the PR only got merged to master which is on version 1.2.0 beta. Could we get the --all-extras flag merged into 1.1 which is installed by default?

[rjurney]

@ecs-jnguyen @kroeschl @neersighted that would be awesome!

[Secrus]

It looks like the PR only got merged to master which is on version 1.2.0 beta. Could we get the --all-extras flag merged into 1.1 which is installed by default?

There won't be any backports to 1.1 at this point. Unless anything breaks upstream (like it was for 1.1.14), there won't be another 1.1 release.

[ecs-jnguyen]

Do we have an estimate on when 1.2 stable will be released?

[neersighted]

Do we have an estimate on when 1.2 stable will be released?

#5586

[github-actions]

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.