💭 PEP 735 – Dependency Groups in pyproject.toml | peps.python.org
Waylon Walker
Learning in Public @_WaylonWalker
Tags
Here's my thought on 💭 PEP 735 – Dependency Groups in pyproject.toml | peps.python.org
PEP 735 describes dependency groups as sets of optional dependencies that are not shipped with the package but intended for development purposes.
The PEP includes an example for groups that include test, docs, typing, and a combo typing-test.
[dependency-groups] test = ["pytest", "coverage"] docs = ["sphinx", "sphinx-rtd-theme"] typing = ["mypy", "types-requests"] typing-test = [{include-group = "typing"}, {include-group = "test"}, "useful-types"]
This is implemented in uv and can be used by several of their commands.
uv sync --group test uv run --group test uv add --group test pytest uv remove --group test pytest uv export --group test uv tree --group test
Dependency Groups are not Extras #
The docs describe extras as being intended to ship with the application and dependency groups intended for development. The spec allows both to exist with the same name, but care should be taken as tools may have different implementations.
Tools MAY choose to provide the same interfaces for installing Dependency Groups as they do for installing extras.
Note that this specification does not forbid having an extra whose name matches a Dependency Group.
Users are advised to avoid creating Dependency Groups whose names match extras. Tools MAY treat such matching as an error.
Note
This post is a thought. It's a short note that I make about someone else's
content online. Learn more about the process
thoughts
This post was a thought by Waylon Walker see all my thoughts at https://waylonwalker.com/thoughts