fix(core): use rglob
to guess local Python modules
#753
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.
Resolves #740.
PR Checklist
docs
is updatedDescription of changes
deptry
doesn't play well with cases where Python packages use PEP 420 and do not have any Python file in the top directory, like shown in the linked issue. I've added a test case that, without the 2nd commit, fails. Usingrglob
instead ofglob
for determining if a directory is a Python package ensures that we recursively search directories, instead of stopping at the first level.