Title: Ensure we are consistently handling optional dev groups vs. extras · Issue #1823 · usethis-python/usethis-python · GitHub
Open Graph Title: Ensure we are consistently handling optional dev groups vs. extras · Issue #1823 · usethis-python/usethis-python
X Title: Ensure we are consistently handling optional dev groups vs. extras · Issue #1823 · usethis-python/usethis-python
Description: A common pattern before PEP735 was to use the PEP621 "extras"/optional dependency groups mechanism. In #1795, we are looking to use the PEP621 style as evidence of dev dependencies, since setup.cfg doesn't support the PEP735 style. There...
Open Graph Description: A common pattern before PEP735 was to use the PEP621 "extras"/optional dependency groups mechanism. In #1795, we are looking to use the PEP621 style as evidence of dev dependencies, since setup.cfg...
X Description: A common pattern before PEP735 was to use the PEP621 "extras"/optional dependency groups mechanism. In #1795, we are looking to use the PEP621 style as evidence of dev dependencies, since...
Opengraph URL: https://github.com/usethis-python/usethis-python/issues/1823
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Ensure we are consistently handling optional dev groups vs. extras","articleBody":"A common pattern before PEP735 was to use the PEP621 \"extras\"/optional dependency groups mechanism.\n\nIn #1795, we are looking to use the PEP621 style as evidence of dev dependencies, since `setup.cfg` doesn't support the PEP735 style.\n\nThere are a few concerns here:\n\n1. We probably need to add some detailed documentation about all the different dependency declaration mechanisms supported by usethis. There's other considerations like Poetry's bespoke style, the deprecated `[tool.uv.dev-dependencies]` style.\n2. Are we supporting the PEP621 style when using uv? What about Poetry?\n2. I question whether we should bother supporting `setup.cfg` at all i.e. questioning #895, or at least whether we should support the idea of dev dependencies with `setup.cfg` (perhaps better to raise an error in such cases, suggesting a `pyproject.toml` migration.) Some tools won't support `setup.cfg` so the implications are tricky; e.g. poetry and uv I don't think support them. In any case something needs to make it clearer to the user that we are ignoring the `setup.cfg` file config if it does have an `[options]` section etc.\n\nOn writing this, I think it's best we close #1795 until this is resolved.","author":{"url":"https://github.com/nathanjmcdougall","@type":"Person","name":"nathanjmcdougall"},"datePublished":"2026-04-06T19:00:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1823/usethis-python/issues/1823"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:d6e5b162-9380-69cf-59d1-b7fc1a0babb5 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 92E2:13DA2D:253D0AB:35CEF9C:6A4D1A71 |
| html-safe-nonce | d0bc7ec9774f958d69a8e17e33bdaa495972df9a067584ef948acef246e6e9e5 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5MkUyOjEzREEyRDoyNTNEMEFCOjM1Q0VGOUM6NkE0RDFBNzEiLCJ2aXNpdG9yX2lkIjoiMjk5NzA1ODYxNTA3MDQ5NzM5MyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | b17131a51cdda226a294c64d32d3dd69720c1232dd5688799551c65b28713b1a |
| hovercard-subject-tag | issue:4213516806 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/usethis-python/usethis-python/1823/issue_layout |
| twitter:image | https://opengraph.githubassets.com/09a9cc697e69b7addbea91121fd9434f1d5c3660883a14f645f1626b245133e2/usethis-python/usethis-python/issues/1823 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/09a9cc697e69b7addbea91121fd9434f1d5c3660883a14f645f1626b245133e2/usethis-python/usethis-python/issues/1823 |
| og:image:alt | A common pattern before PEP735 was to use the PEP621 "extras"/optional dependency groups mechanism. In #1795, we are looking to use the PEP621 style as evidence of dev dependencies, since setup.cfg... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | nathanjmcdougall |
| hostname | github.com |
| expected-hostname | github.com |
| None | bcb4661e6fb4fe8b394c51ea02ccdb2236d40dc59afc75a3bbba50bf6517134c |
| turbo-cache-control | no-preview |
| go-import | github.com/usethis-python/usethis-python git https://github.com/usethis-python/usethis-python.git |
| octolytics-dimension-user_id | 216362695 |
| octolytics-dimension-user_login | usethis-python |
| octolytics-dimension-repository_id | 842189705 |
| octolytics-dimension-repository_nwo | usethis-python/usethis-python |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 842189705 |
| octolytics-dimension-repository_network_root_nwo | usethis-python/usethis-python |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | fb70bd3c4b2bec429781b65419e912c66e2d5581 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width