fpgmaas/deptry

Release 0.12.0

fpgmaas opened this issue · 2 comments

fpgmaas commented

What's Changed

This release introduces a significant change to the command-line flags and configuration options to make use of the error codes introduced in release 0.10.0.

Code Issue
DEP001 Missing dependency
DEP002 Unused/obsolete dependency
DEP003 Transitive dependency
DEP004 Misplaced development dependency

Features

  • Replaced --skip-unused, --skip-obsolete, --skip-missing, --skip-misplaced-dev flags: We have replaced the currently existing flags with the more generalized --ignore flag. Now, instead of skipping types of checks, you can specify the exact error codes to ignore using the --ignore flag (e.g., deptry . --ignore "DEP001,DEP002" to ignore checking for missing and unused dependencies).

The changes are also reflected in pyproject.toml. For example,

[tool.deptry]
skip_missing = true
skip_unused = true

is superseded by

[tool.deptry]
ignore = ["DEP001", "DEP002"]
  • Replaced --ignore-unused, --ignore-obsolete, --ignore-missing, --ignore-misplaced-dev flags: Previously, specific checks for spefific dependencies/modules could be ingored using the --ignore-<code> flags. We are replacing these flags with the more generalized --per-rule-ignores flag. This flag allows you to specify dependencies that should be ignored for specific error codes, offering granular control over which errors are ignored for which dependencies. For instance, deptry . --per-rule-ignores DEP001=matplotlib,DEP002=pandas|numpy means DEP001 will be ignored for matplotlib, while DEP002 will be ignored for both pandas and numpy.

The changes are also reflected in pyproject.toml. For example,

[tool.deptry]
ignore_missing = ["matplotlib"]
ignore_unused = ["pandas", "numpy"]

is superseded by

[tool.deptry.per_rule_ignores]
DEP001 = ["matplotlib"]
DEP002 = ["pandas", "numpy"]

Please note that while the legacy arguments are still functional as of Deptry 0.12.0, we do plan to remove them in a future 1.0.0 release.

Bug fixes

Full Changelog: 0.11.0...0.12.0

fpgmaas commented

@mkniewallner Draft for the new release notes. Curious for your thoughts!

mkniewallner commented

Now that we have a changelog in the repository, we can directly create a pull request with the release notes, to make it easier to suggest changes if needed 🙂

Please note that while the legacy arguments are still functional as of Deptry 0.12.0, we do plan to deprecate them in a future 1.0.0 release.

I believe we plan to remove them, since 0.12.0 will effectively deprecate them?

feat(poetry): consider all groups for dev dependencies

We can move that to Features section as well, to be consistent with other changelogs, and probably drop the feat:

Consider all groups for Poetry dev dependencies

We should probably add #426 to Bug Fixes section as well, since some users may end up with this error.
Proposal for the changelog entry:

Handle `SyntaxError` when parsing imports