Development Dependencies In pyproject.toml

[sinoroc]

@Zomatree

It seems like that discussions has gone pretty stale, I feel like this is something that should really be added. I’d be willing to write a PEP if that is was is needed for this to be pushed into being a real feature.

I guess if you manage to write an objective summary of the discussion so far, that would be a great way to resume the discussion and that would probably keep the level of motivation required to get back on the topic as low as possible for others. People do not necessarily want to go back and read the whole (long) discussion (again). I know I don’t want to and I would prefer a summary.

Reading only the bottom of that previous discussion, one can notice there seemed to have been some kind of relative agreement on this suggestion:

Adding a non-metadata installer-only `dev-dependencies` table to pyproject.toml

I’m wondering if there’s another way. Since the original intention is to have a dependency group that does not show up as extras, maybe we should instead provide a way to declare an optional dependency group as (air-quotes) non-public? Say [project.optional-dependencies] auth = ["cryptography"] tests = ["pytest"] [project] extras = ["auth"] If the extras key is missing, the default is to populate the value with all keys in optional-dependencies. If it’s explicitly given, it lists the extras …

So if you want to write something (a PEP?) maybe that is a good place to start. And I guess you would need to have some kind of agreement / buy-in (or even better some proof of concept implementations) from at least one or two tools (I guess dev workflow tools such as Hatch, PDM, and Poetry probably make the most sense, but also tox, nox, and “task runners” such as doit, invoke, and taskipy could be very good candidates as well).