Repository navigation
Flag to install all extras #3413
Description
- 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:
- 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.
- Listing each extra specifically in the developer instructions.
- 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
Reacted by Christian Riedel, Alexey Yurkevich, Franck Nijhof, Rafal Skolasinski, Johannes Wienke, Antoine, Leah Einhorn, Conchylicultor, Danil Troshnev, Jacek Jabłoński and 14 more
Activity
sinoroc commentedon Nov 25, 2020
Related: #3369
thclark commentedon Apr 8, 2022
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
.devcontainerfile if we add extras to the library we're developing... so sounds like the same use case as the OP.abn commentedon Apr 9, 2022
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 commentedon Apr 10, 2022
--all-extraswould 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 commentedon Apr 15, 2022
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: #5452rjurney commentedon Jul 19, 2022
Any idea when this will be released?
ecs-jnguyen commentedon Jul 27, 2022
It looks like the PR only got merged to master which is on version 1.2.0 beta. Could we get the
--all-extrasflag merged into 1.1 which is installed by default?rjurney commentedon Jul 27, 2022
@ecs-jnguyen @kroeschl @neersighted that would be awesome!
Secrus commentedon Jul 27, 2022
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 commentedon Jul 28, 2022
Do we have an estimate on when 1.2 stable will be released?
neersighted commentedon Jul 29, 2022
#5586
github-actions commentedon Mar 1, 2024
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.