Unless --exclude is used, deptry excludes files found in common ignore files (.gitignore, .ignore, $HOME/.config/git/ignore. ...), by using ignore Rust crate. The default behaviour has been changed, so that now:
git-related ignore rules (.gitignore, $HOME/.config/git/ignore, ...) are only used if deptry is run inside a git repository
.gitignore files that are in parent directories of the git repository from where deptry is run are not used (previously, deptry would traverse parent directories up to the root system)
If you were using .gitignore files for non-git repositories, you might want to switch to .ignore files, or use --extend-exclude.
Requirements files parsing
deptry now uses requirements-parser to parse dependencies from requirements files, meaning that it can now extract nested requirements files referenced in other requirements files without having to explicitly configure it in deptry.
With the default configuration, when parsing requirements.txt, both httpx and click will now be listed as dependencies by deptry, while previously, only httpx was, unless deptry was instructed about cli-requirements.txt by using --requirements-files. This new behaviour also impacts development requirements files, that can be overridden by using --requirements-files-dev.
Python 3.8 support dropped
Support for Python 3.8 has been dropped, as it has reached its end of life.
Features
deptry now detects development dependencies from [dependency-groups] section, introduced by PEP 735 (#892)
Unless --exclude is used, deptry excludes files found in common ignore
files (.gitignore, .ignore, $HOME/.config/git/ignore. ...), by using ignore
Rust crate. The default behaviour has been changed, so that now:
git-related ignore rules (.gitignore, $HOME/.config/git/ignore, ...) are only used if deptry is run inside a git
repository
.gitignore files that are in parent directories of the git repository from where deptry is run are not
used (previously, deptry would traverse parent directories up to the root system)
If you were using .gitignore files for non-git repositories, you might want to switch to .ignore files, or use
--extend-exclude.
Requirements files parsing
deptry now uses requirements-parser to parse dependencies from
requirements files, meaning that it can now extract nested requirements files referenced in other requirements files
without having to explicitly configure it in deptry.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps deptry from 0.17.0 to 0.21.1.
Release notes
Sourced from deptry's releases.
... (truncated)
Changelog
Sourced from deptry's changelog.
... (truncated)
Commits
54b54a0
docs(changelog): add 0.21.1 release notes (#946)2a9da88
fix(dependency_getter): handle strings forsetuptools
dynamic dependencies ...40765df
chore(deps): lock file maintenance (#943)c7b7a07
chore(deps): lock file maintenance (#942)b4f5bb4
fix(deps): update rust crate pyo3 to v0.22.6 (#940)78697aa
chore(deps): update uv-version to v0.5.1 (#941)af07798
chore(deps): update uv-version to v0.4.30 (#939)f200460
chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.7.3 (#938)a59e388
chore(deps): update dependency mkdocs-material to v9.5.44 (#937)3557308
docs(changelog): add 0.21.0 release notes (#907)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show