)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"705252ec35370f24a9134fc36e3521af093b484a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b7efacaa_2afd380f","updated":"2026-05-11 07:31:07.000000000","message":"I don\u0027t understand yet why this feature is required for OpenStack, can you add some more context? the requirements team is already struggling to keep things working, adding more complexity seem counter-productive to me if it can be avoided. maybe you want to fully join the team as a maintainer in order to ensure that this and other things are kept in good shape?","commit_id":"3b80226b6025682b891c5ee0218b69f2f29b1214"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"c8ad4ebb85115e1b6c823c72428ae956b69af6ec","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f2d61a6a_067463b8","updated":"2026-05-25 16:22:47.000000000","message":"fyi I\u0027ve proven this works in https://review.opendev.org/c/openstack/openstacksdk/+/953484","commit_id":"3b80226b6025682b891c5ee0218b69f2f29b1214"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"8585c67c4399c635dbb8b467c20a2720c9bac79d","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f8198543_e2bc4596","in_reply_to":"b7efacaa_2afd380f","updated":"2026-05-11 10:04:52.000000000","message":"\u003e I don\u0027t understand yet why this feature is required for OpenStack, can you add some more context? the requirements team is already struggling to keep things working, adding more complexity seem counter-productive to me if it can be avoided. \n\nRegarding the feature itself, this is covered in much greater detail in the PEP but dependency groups are intended to allow users to gather development dependencies (as opposed to runtime dependencies) for things like testing (stestr, testtools, ...), linting (mypy, hacking, ...) and documentation (sphinx). You can see an example patch migrating extras to dependency groups from @fungi@yuggoth.org [here](https://review.opendev.org/c/opendev/bindep/+/945403). At the moment, there\u0027s nothing to stop people using dependency groups in their `pyproject.toml` files but any dependencies specified there won\u0027t be verified against our upper-constraints.\n\nRegarding why _we_ want to use this feature, I\u0027m trying to keep us relatively up-to-speed with Python packaging. Lack of investment in all things packaging [*] got us into the `pkg_resources` mess we are still struggling with. This builds on earlier work to add support for `pyproject.toml` files here to close this gap in (I think/hope) a relatively simple, readable manner.\n\n\u003e maybe you want to fully join the team as a maintainer in order to ensure that this and other things are kept in good shape?\n\nI\u0027m always happy to help out, but it\u0027s probably worth figuring out what commitment you\u0027d be looking for from me, given how much I already have on my plate between SDK, Oslo and Nova (to say nothing of all my k8s work). I am pretty familiar with this tooling now though at least.\n\n[*] tbc, it\u0027s not all us and IMO the PyPA have a lot to answer for, but there are some things we can directly control and some things we can\u0027t","commit_id":"3b80226b6025682b891c5ee0218b69f2f29b1214"}]}