# PEP 735: Dependency Groups in pyproject.toml

**URL:** <https://discuss.python.org/t/pep-735-dependency-groups-in-pyproject-toml/39233>\
**Category:** Standards\
**Created:** [November 20, 2023, 9:50pm UTC](https://discuss.python.org/t/pep-735-dependency-groups-in-pyproject-toml/39233 "2023-11-20T21:50:35Z")\
**Posts on this page:** 1\
**Showing post:** 312

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [October 10, 2024, 1:09pm UTC](https://discuss.python.org/t/pep-735-dependency-groups-in-pyproject-toml/39233/312 "2024-10-10T13:09:20Z")

</div>

I have now reviewed this PEP (and the thread here - phew!) and I’m pleased to say that PEP 735 (Dependency Groups) is **accepted** 🎉

Congratulations, @sirosen - this was a long, complex discussion and you handled it really well, keeping things on track without shutting down important debates. For a first PEP, it was a very impressive performance!

> [@sirosen](#):
>
> The tale of this PEP has been, in summary, “Smaller, narrower, more focused!”

This is a very good point, and in my opinion was a key factor in the success of the PEP. It would have been very easy to try to support everything in one go, and end up with a complex specification with a bunch of incompletely understood edge cases. By deferring complex questions for future extensions, you’ve established a solid base for the feature without locking us out of further capabilities in future. That’s a useful lesson for authors of other PEPs to learn.

---

_[View the full topic](https://discuss.python.org/t/pep-735-dependency-groups-in-pyproject-toml/39233)._