> On Jan 1, 2015, at 9:11 PM, Tres Seaver <tsea...@palladion.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01/01/2015 04:57 PM, Donald Stufft wrote: > >> I’m pretty sure the problem with setup.py develop and setup.py install >> is because they are installed as eggs more or less and setuptools >> probably doesn’t support it. pip install <whatever> installs it >> unpacked so it’ll rely on built in importing. > > I'm puzzled by that notion: 'setup.py develop' and 'setup.py install' > have worked for a decade with namespace packages, as long as the __init__ > for them does the Right Thing (using either pkg_resources or pkgutil). > > What has never worked properly is mixing pip installation of namespace > packages with easy_install installation of packages in the same > namespace: pip's "install in one directory without fixups" stragedy > screws up the __path__ for the namespace packages installed elsewhere. >
Why are you puzzled by the notion that something designed to work with a one mechanism for a particular feature probably does not work with a newer, different mechanism for a particular feature? My assumption is that setuptools is ensuring that the __init__.py files are being written (or the nspkg or whatever, I forget which files are used in which cases) which is breaking the PEP420 “implicit” namespace packages. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
