Support for PEP 735: Dependency Groups in pyproject.toml
#8090
Comments
zanieb
added
enhancement
zanieb
changed the title
pyproject.toml
|
I'm just curious, but will there be a "dev" dependency group that supplants [tool.uv]
dev-dependencies = …or is it up to the user to specify the |
|
Dependency-groups don't allow self-dependencies, so |
|
I noticed there is no mention of constraints in the pep. Dev-constraints is
super useful to me . Do you think this concept will continue to be
supported as 735 is implemented?
…On Fri, Oct 11, 2024, 20:34 Henry Schreiner ***@***.***> wrote:
Dependency-groups don't allow self-dependencies, so dev-dependencies =
["<self>[test]"] wouldn't be replaceable with dependency groups. Also, I
think/hope that dependency groups are going to feed into a new environment
and task system. :)
—
Reply to this email directly, view it on GitHub
<#8090 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABY5SZNHP7RTAJMIFAHFSW3Z3CKEHAVCNFSM6AAAAABPW2Q3ESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGMZTGMRZGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Is this explicitly banned? I think |
I'm not sure yet. This is a significant open question I must address before adding support. |
I don't see any reason that we wouldn't apply constraints to the dependencies in the groups. Do you need a separate set of constraints? |
|
I only see this section, but I don't see any other discussion in the finalized PEP of self-references of project dependencies in dependency groups. |
I am asking about the equivalent of here is an example from pyproject.toml from a repo that contains dags: cloud composer docs 1 difference from the other issue is we are not using the official airflow constraints file from the url (this is what i used to use before we moved to the managed airflow). Right now I am copying the list of installed packages into my pyproject.toml file. |
|
@dschneiderch -- Apologies if I'm misunderstanding but I think |
|
Perfect! Wasn't sure if that metadata field was going to be redesigned
alongside dev-dependencies .
…On Sat, Oct 12, 2024, 14:02 Charlie Marsh ***@***.***> wrote:
@dschneiderch <https://github.com/dschneiderch> -- Apologies if I'm
misunderstanding but I think constraint-dependencies will just continue
to be the right thing to use there.
—
Reply to this email directly, view it on GitHub
<#8090 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABY5SZLLZYROQTHBXX5QSVLZ3GE7HAVCNFSM6AAAAABPW2Q3ESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGY4TSMBRGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Duplicates #5632 -> either this or the other one could probably be closed. |
|
Would love to get it in ... PR is coming I see :) |
|
Same, looking forward to using it in the Airflow repo |
Part of #8090 As a basic first step, we parse these groups defined in `pyproject.toml` files.
Part of #8090 Adds the ability to add and remove dependencies from arbitrary groups using `uv add` and `uv remove`. Does not include resolving with the new dependencies — tackling that in #8110. Additionally, this does not yet resolve interactions with the existing `dev` group — we'll tackle that separately as well. I probably won't merge the stack until that design is resolved.
… in `uv lock` (#8110) Part of #8090 Adds the ability to include a group (`--group`) in the sync or _only_ sync a group (`--only-group`). Includes all groups in the resolution, which will have the same limitations as extras as described in #6981. There's a great deal of refactoring of the "development" concept into "groups" behind the scenes that I am continuing to defer here to minimize the diff. Additionally, this does not yet resolve interactions with the existing `dev` group — we'll tackle that separately as well. I probably won't merge the stack until that design is resolved. The current proposal is that we'll just "combine' the `dev-dependencies` contents into the `dev` group.
Part of #8090 As a basic first step, we parse these groups defined in `pyproject.toml` files.
Part of #8090 Adds the ability to add and remove dependencies from arbitrary groups using `uv add` and `uv remove`. Does not include resolving with the new dependencies — tackling that in #8110. Additionally, this does not yet resolve interactions with the existing `dev` group — we'll tackle that separately as well. I probably won't merge the stack until that design is resolved.
… in `uv lock` (#8110) Part of #8090 Adds the ability to include a group (`--group`) in the sync or _only_ sync a group (`--only-group`). Includes all groups in the resolution, which will have the same limitations as extras as described in #6981. There's a great deal of refactoring of the "development" concept into "groups" behind the scenes that I am continuing to defer here to minimize the diff. Additionally, this does not yet resolve interactions with the existing `dev` group — we'll tackle that separately as well. I probably won't merge the stack until that design is resolved. The current proposal is that we'll just "combine' the `dev-dependencies` contents into the `dev` group.
…roups (#8266) Part of #8090 Adds the ability to read group inclusions (`include-group = <name>`) in the `pyproject.toml`. Resolves groups into concrete dependencies for resolution. See #8110 for a bit more commentary on deferred work. --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
Part of #8090 As a basic first step, we parse these groups defined in `pyproject.toml` files.
Part of #8090 Adds the ability to add and remove dependencies from arbitrary groups using `uv add` and `uv remove`. Does not include resolving with the new dependencies — tackling that in #8110. Additionally, this does not yet resolve interactions with the existing `dev` group — we'll tackle that separately as well. I probably won't merge the stack until that design is resolved.
… in `uv lock` (#8110) Part of #8090 Adds the ability to include a group (`--group`) in the sync or _only_ sync a group (`--only-group`). Includes all groups in the resolution, which will have the same limitations as extras as described in #6981. There's a great deal of refactoring of the "development" concept into "groups" behind the scenes that I am continuing to defer here to minimize the diff. Additionally, this does not yet resolve interactions with the existing `dev` group — we'll tackle that separately as well. I probably won't merge the stack until that design is resolved. The current proposal is that we'll just "combine' the `dev-dependencies` contents into the `dev` group.
…roups (#8266) Part of #8090 Adds the ability to read group inclusions (`include-group = <name>`) in the `pyproject.toml`. Resolves groups into concrete dependencies for resolution. See #8110 for a bit more commentary on deferred work. --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
Part of #8090 As a basic first step, we parse these groups defined in `pyproject.toml` files.
Part of #8090 Adds the ability to add and remove dependencies from arbitrary groups using `uv add` and `uv remove`. Does not include resolving with the new dependencies — tackling that in #8110. Additionally, this does not yet resolve interactions with the existing `dev` group — we'll tackle that separately as well. I probably won't merge the stack until that design is resolved.
… in `uv lock` (#8110) Part of #8090 Adds the ability to include a group (`--group`) in the sync or _only_ sync a group (`--only-group`). Includes all groups in the resolution, which will have the same limitations as extras as described in #6981. There's a great deal of refactoring of the "development" concept into "groups" behind the scenes that I am continuing to defer here to minimize the diff. Additionally, this does not yet resolve interactions with the existing `dev` group — we'll tackle that separately as well. I probably won't merge the stack until that design is resolved. The current proposal is that we'll just "combine' the `dev-dependencies` contents into the `dev` group.
…roups (#8266) Part of #8090 Adds the ability to read group inclusions (`include-group = <name>`) in the `pyproject.toml`. Resolves groups into concrete dependencies for resolution. See #8110 for a bit more commentary on deferred work. --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
This PEP was just accepted — we plan to support it. We'll track it here.
The implementation can be tracked in #8272
The text was updated successfully, but these errors were encountered: