Barry A. Warsaw added the comment:
https://docs.python.org/3/reference/import.html#regular-packages
Regular packages have __init__.py files and namespace packages do not.
"Implicit non-namespace packages" aren't really A Thing.
This design choice is deliberate; namespace packages
Girts Folkmanis added the comment:
> What's the difference between "namespace packages and implicit non-namespace
> packages"?
To me, the semantic difference is that "namespace packages" are what is used
when you have "foo.bar" and "foo.baz" come from different distributions
Eric V. Smith added the comment:
What's the difference between "namespace packages and implicit non-namespace
packages"? I think those are the same thing, aren't they?
--
nosy: +barry, brett.cannon, eric.smith
___
Python tracker
New submission from Girts Folkmanis :
importlib.resources does not seem to work with packages that don't have
__init__.py present. Since 3.3+ generally there is no need to create empty
__init__.py, as directories are automatically treated as packages even without
the file present. So my
