#18: Add checker for unused and undeclared dependencies #20
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.
The PR contains configuration examples for deptry and fawltydeps.
The main differences are:
deptry
unable to find such undeclared dependencies ascelery
,fawltydeps
requires fine-grained configuration to avoid false positives likedjango
(Django
inpyproject.toml
).deptry
converts package names tocamel_case
if necessarydjango-environ
(imported asenviron
)deptry
requires more configuration forDjango
projects to avoid false positives for packages which are not used in codebase (for example,django-cors-headers
)fawltydeps
unable to resolve packages from private pypi (core-python-client
, .etc)As a result, neither of these tools is good enough. But they can be used in tandem to achieve desired behavior. Unfortunately, with extra configuration.
Detailed output could be found in deptry_worklogs_toggl_output.txt and fawltydeps_worklogs_toggl_output.txt
Resolves #18