feat(core): handle local modules without __init__.py
#285
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.
PR Checklist
docs
is updatedDescription of changes
Since PEP 420, it is not required for Python modules to have an
__init__.py
to be considered a Python module.We also today only consider directories and not Python files.
This PR handles this case by relaxing
_get_local_modules
method to account for 2 things:__init__.py
, by checking for any Python file.py
extension)Tests have been updated to reflect what this implies for projects using an
src
directory structure.