-
-
Notifications
You must be signed in to change notification settings - Fork 610
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
Eventually implement support for the PEP 735 "dependency groups" #2062
Comments
What are you planning to have for dependency group support? An option to collect only such dependencies, or alongside with normal and build deps? And the possibility to collect only specified dependency groups? |
Same as #1960 attempted, just in the proper place. Semantically, dependency groups don't imply including runtime dependencies so they should definitely be collected and output separately. However, we shouldn't actively prevent combining them with other deps (runtime, or runtime+extra, or other dependency groups; though the latter seems to be covered by the PEP itself). |
IIUC that would mean actually creating an option like |
Aren't the past two the same? |
Yes, this was unintended. Is the rest of my assumption valid? |
I think so. It of course could be iterated on during a PoC review.. |
What's the problem this feature will solve?
It's just a new source of deps and an extension to the first round of the
pyproject.toml
runtime deps resolution.Describe the solution you'd like
$sbj. If somebody's interested in making a PoC, it's probably fine to start drafting something already. Need to wait for the PEP acceptance to actually merge it in, though.
Alternative Solutions
... not doing this?
Additional context
Refs:
The text was updated successfully, but these errors were encountered: