-----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. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlSl/kEACgkQ+gerLs4ltQ4aYQCcDImoKfLr3Xb+tkFSY9x8Oinh QT8AoNDKmxVoqdX3UMnsUg1ktZbqukZg =CPP5 -----END PGP SIGNATURE----- _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig