we do have non-empty _init_.py files scattered aro...
# general
b
we do have non-empty init.py files scattered around, but not in any consistent way
h
Sorry I was asleep and trying to catch up. How are you using namespace packages? Are you using PEP 440 with no
__init__.py
files, or setuptools-style like
__import__(' pkg_resources').declare_namespace(__name__)
Bump on this. In 1.30, Pants had kind of magical handling of
__init__.py
files. It was tricky to get namespace packages working in 1.30 A major improvement of 2.0 is to fix this so that Pants does the right thing with
__init__.py
files