I hate to bring this up again after such a long while, but after reading through dev dependencies in pyproject.toml, searching for any new updates for this specific issue, and reading this thread again I am wondering where we stand on some potential future for this.
I quite like the proposal as discussed by @uranusjr here, or literally any other way including just throwing the dev. dependencies into the what-eventually-will-be-public namespace for extras on a package ala optional-dependencies.
The usecase here is one of simplified tooling, new user onboarding, and custom tooling to manage the current “73”
Summary
(I feel like when I look at the landscape of projects, the top level workspace is cluttered with many .$tool-config, requirements.$thing.txt, etc.)
requirements-*.txt files or tool.*.dev-dependencies.
The benefits of this include enhancing the ecosystem coherence and (imo nicely) simplifying developer experiences, which cannot be overstated. Emergent tooling (re: rye and uv) give hope to a unified option in the ecosystem but that hope trickles upstream into the orators of the Python packaging standards.
So… I advocate for the drafting of a PEP to formalize this proposal (I’d love to help!)… if we can move beyond our current stale discussions to implementation, addressing any lingering questions/stalemates, we would be fulfilling a widely acknowledged need within our community.
again, sorry for the necro post - but I have yet to find a newer discussion or movement elsewhere on what I feel to be an exciting feature addition/standardization cemented