You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/_includes/pyproject.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,9 +110,14 @@ work to call the app (`__name__` will be `"__main__"` in that case).
110
110
111
111
### Development dependencies
112
112
113
-
The proper way to specify dependencies exclusively used for devlopment tasks (such as `pytest`, `ruff`, packages for generating documentation, etc.) is to use dependency-groups.
114
-
Dependency-groups are recommended over requirement files because they are formally standardized (i.e. they will be more portable going forward) and they are more composable.
115
-
In contrast with extras, dependency-groups are not available when installing your package via PyPI, but they are available for local installation (and can be installed separately from your package); the `dev` group is even installed, by default, when using `uv`.
113
+
The proper way to specify dependencies exclusively used for development tasks
114
+
(such as `pytest`, `ruff`, packages for generating documentation, etc.) is to
115
+
use dependency-groups. Dependency-groups are recommended over requirement files
116
+
because they are formally standardized (i.e. they will be more portable going
117
+
forward) and they are more composable. In contrast with extras,
118
+
dependency-groups are not available when installing your package via PyPI, but
119
+
they are available for local installation (and can be installed separately from
120
+
your package); the `dev` group is even installed, by default, when using `uv`.
116
121
Here is an example:
117
122
118
123
```toml
@@ -129,9 +134,9 @@ You can include one dependency group in another. Most tools allow you to install
129
134
groups using `--group`, like `pip` (25.1+), `uv pip`, and the high level `uv`
130
135
interface. It's possible to install a package's dependency group without
131
136
installing the package itself, but usually you'll want to instruct your tool to
132
-
install both (the high level `uv` interface does this automatically).
133
-
Nox, Tox, and cibuildwheel all support groups, too. The `dependency-groups`
134
-
package also provides tools to get the dependencies.
137
+
install both (the high level `uv` interface does this automatically). Nox, Tox,
138
+
and cibuildwheel all support groups, too. The `dependency-groups` package also
0 commit comments