Correct implementation of pkgutil style namespace (Fixes #144) #145
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.
Change to correct use of pkgutil style namespace packages as documented https://packaging.python.org/guides/packaging-namespace-packages/#pkgutil-style-namespace-packages and illustrated in https://github.com/pypa/sample-namespace-packages/tree/master/pkgutil
See #144 for a longform attempt at explaining this change. The short explanation is that this package confuses the two different methods of implementing namespace packages and this change corrects the implementation to the (Python 2.3+ and Python 3.x compatible) pkgutil style method.
Note: at the moment the
namespace_packages
directive is completely ignored, if you add the "luma" package topackages
(in addition tonamespace_packages
) thensetup.py build
returns an error because it is expecting a pkg_resources style namespace package:Note: in the linked example the
find_packages()
method returns the "namespace" package as if it were an ordinary package.