Declare dev dependencies using PEP 735 – Dependency Groups in pyproject.toml #2672
+25
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unlike using
[extras], PEP 735 – Dependency Groups in pyproject.toml allows declaratively configuring Project dependencies that won't end up exposed in the published package.Here I have set a
devdependency group, which is the canonical group name to specify dev-dependencies for which certain package managers can take shortcuts (for exampleuv sync,uv pip install --dev,poetry sync,poetry install --dev,pipenv install --dev, etc. will install dev dependencies by default).I have added 2 subgroups (
checkersandtype-checkers) for minimal dependency install on the CI. These group names match the CI job names.This requires pip >=25.1 to use with pip:
pip install --group=dev. Pip 25.1 dropped support for Python 3.8, but luckily since this is only used for checkers in CI, I don't need to wait for #2413 .