New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scan folders that do not contain an __init__.py #68
Comments
For maintainers: Should we update the documentation to explicitly refer to this change in PEP 420, especially since we dropped support for Python 3.4 and older? Or should we update Venusian itself? Side note, if you document docstrings in packages with Sphinx, you might want to still use an |
This is a limitation in For example:
Take note that
Compare that to:
The two are treated very different from each other. Unfortunately this is not something that we can paper over in venusian. |
Do note that this issue will cause failures in other software too, which uses similar lookup methods. I believe that |
We might be able to adapt what Sphinx has done with |
That walks the file system tree manually, instead of relying on the importer to do its thing. I'm wondering if there is any side effects there that we'd have to be aware of if we went down that same path. Right now venusian has to not care if the package being scanned is a zip file or not, if we go down the route of manually trying to walk the tree, we'd need special handling for dealing with zipped files or other types of importers. |
Python 3.3+ no longer requires
__init__.py
to import a folder as a module.https://stackoverflow.com/questions/37139786/is-init-py-not-required-for-packages-in-python-3-3
Venusian does not scan a folder if it lacks an
__init__.py
.That means a folder must explicitly have an
__init__.py
for venusian to scan it.Not sure if this is something that should be fixed, but just making a note for consideration in case future developers stumble on this.
The text was updated successfully, but these errors were encountered: