# 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:** 134

<div class="post-metadata">

**Author:** ![sinoroc](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sinoroc/32/1607_2.png) [@sinoroc](https://discuss.python.org/u/sinoroc)\
**Post date:** [November 27, 2023, 6:09pm UTC](https://discuss.python.org/t/pep-735-dependency-groups-in-pyproject-toml/39233/134 "2023-11-27T18:09:27Z")

</div>

> [@sirosen](#):
>
> I’m fully okay with making that kind of move _if_ we can explain how the dependency group data could be augmented

```toml
[dependency-groups]
# `.` is the only path-like value accepted and it stands for the current project 
production = ["."]
test = ["pytest", "."]

```

```toml
index-url = "https://corporate-repo.test/simple/"

[mypackage]
editable = true

[common-core]
path = "../commone-core"
editable = true

[pytest]
version = "<7.4"

```

Basically it is [this idea](https://discuss.python.org/t/proposal-overrides-for-installers/23666).

Maybe we can play with having one set of default “overrides” (i.e. concrete dependencies) per dependency group, as long as it is easy to opt-out of those defaults and use another set of overrides instead.

---

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