Conflict between egg and standard package with same namespace
In my setup I have a zopyx.slimp egg inside site-package and a package zopyx.txng3. With this setup I can not longer import files from the zopyx.txng3 package. ajung@galactica:~> ls /opt/python-2.4.3/lib/python2.4/site-packages/zopyx* /opt/python-2.4.3/lib/python2.4/site-packages/zopyx.slimp-0.2.0-py2.4.egg /opt/python-2.4.3/lib/python2.4/site-packages/zopyx: __init__.py __init__.pyc txng3 ajung@galactica:~> python2.4 Python 2.4.4 (#4, Oct 19 2006, 21:09:46) [GCC 4.1.0 (SUSE Linux)] on linux2 Type "help", "copyright", "credits" or "license" for more information.
import zopyx.txng3 Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named txng3 import zopyx.slimp
After removing the egg it is possible to import zopyx.txng3 again. Is this a bug or setuptools misconception? Andreas
At 09:09 PM 6/13/2007 +0200, Andreas Jung wrote:
In my setup I have a zopyx.slimp egg inside site-package and a package zopyx.txng3. With this setup I can not longer import files from the zopyx.txng3 package.
ajung@galactica:~> ls /opt/python-2.4.3/lib/python2.4/site-packages/zopyx* /opt/python-2.4.3/lib/python2.4/site-packages/zopyx.slimp-0.2.0-py2.4.egg
/opt/python-2.4.3/lib/python2.4/site-packages/zopyx: __init__.py __init__.pyc txng3
What's inside of __init__.py here? If it's not a namespace package declaration, it's not going to work. Specifically, both projects must declare 'zopyx' as a namespace package, in order to distribute subpackages of it separately.
participants (2)
-
Andreas Jung -
Phillip J. Eby