[Bug 563060] Re: pkg_resources.require() throws a DistributionNotFound exception if python-setuptools is not installed
yes, this affects many packages (almost any namespace package) and should really be fixed at the build helper level. We shouldn't need to apply the same patch to every zope.* package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/563060 Title: pkg_resources.require() throws a DistributionNotFound exception if python-setuptools is not installed To manage notifications about this bug go to: https://bugs.launchpad.net/distribute/+bug/563060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688335] Re: superfluous __init__.py generates import errors
This __init__.py is included because it causes other breakage if removed. Please see a previous discussion on removing this: https://bugs.launchpad.net/van.pydeb/+bug/619294 That bug contains a test case which fails when the __init__.py is removed. Background reading on the breakage: http://mail.python.org/pipermail/distutils-sig/2009-May/011730.html Consistency in what is broken is probably more important than fixing one thing only to break another;) So I'd rather we didn't try fix this until the test case in the van.pydeb bug passes without the __init__.py. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688335 Title: superfluous __init__.py generates import errors -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688335] Re: superfluous __init__.py generates import errors
In discussion on distutils-sig it was decided that having the zope/__init__.py available is the right thing to do and will be standard in dh_python2 in future. So this is not a bug. Also the OP discovered that the bug really biting him was https://bugs.launchpad.net/ubuntu/+source/distribute/+bug/576434 ** Changed in: zope.interface (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688335 Title: superfluous __init__.py generates import errors -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619294] Re: Do not add namespace packages to depends
When the builder installs the package (setup.py install --single- version-externally-managed, and more specifically, setuptools' install_lib command), __init__.py files are skipped, because they would conflict if installed by multiple packages . Instead, setuptools' install_egg_info command installs a *-nspkg.pth file that ensures that the package exists -- if an __init__.py file exists, it is used, but if not, a module is added to sys.modules, so imports work anyway. Since all zope projects use setuptools, they don't need the __init__.py files. Thanks, that info helped me find this: http://mail.python.org/pipermail/distutils-sig/2009-May/011730.html I made a test (attached), it fails without the __init__.py in the namespace package for me like this: ji...@ec2-staging:~/test_ns$ python test.py ji...@ec2-staging:~/test_ns$ sudo mv /usr/lib/python2.5/site-packages/zope/__init__.py* tmp/ ji...@ec2-staging:~/test_ns$ python2.5 test.py Traceback (most recent call last): File test.py, line 1, in module import zope.testpackage ImportError: No module named testpackage ji...@ec2-staging:~/test_ns$ sudo mv tmp/__init__.py* /usr/lib/python2.5/site-packages/zope/ This test failed Debian Lenny and Squeeze machines for python 2.5 and 2.6. Could you check that the same occurs in Ubuntu? You need to extract the tarball in your home directory and have python-zope.interface and python-zope.event installed. P.S. The test is possibly destructive to the machine it runs on, so use one you don't care about. Unless we can get the above to work, I think we should not commit your patch. I can add a virtual python-zope.app to some random package, because I can't think of the most important zope.app.* library like zope.interface is. But I would like to avoid depending on python-zope.app at all, that's why I filed this bug. zope.app.publisher seems to have no zope.app.* dependencies and is pretty central. Failing that, I think there's a good argument for putting the virtual package for zope.app.* in either python-zope.interface or python-zope.event. ** Attachment added: test_ns.tar.gz https://bugs.launchpad.net/van.pydeb/+bug/619294/+attachment/1513321/+files/test_ns.tar.gz -- Do not add namespace packages to depends https://bugs.launchpad.net/bugs/619294 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619294] Re: Do not add namespace packages to depends
That comment is pretty old :) The use of virtual namespace packages in Debian turned it into a reasonably elegant solution. For the patch to be committed, we'll need more proof that not having the __init__.py for a namespace package works properly and doesn't make us vulnerable to setuptools/distribute vagaries and weird setups. Honestly, I'd rather play it safe and depend on the good-old-fashioned python import with the __init__.py. It is surprising that importing without the __init__.py worked at all. You made a comment about requiring extra packages. I presume you mean packages like python-zope? We resolved that in debian by using a Virtual package. The __init__.py file is shipped in python- zope.interface which Provides: python-zope. see: http://packages.debian.org/sid/python-zope You can use diversions (dpkg-divert) in case you need multiple packages to provide the virtual namespace package. -- Do not add namespace packages to depends https://bugs.launchpad.net/bugs/619294 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487536] Re: package python-zconfig 2.7.1-1 failed to install/upgrade:
Seems to be a filesystem conflict with the zope3 package: pycentral pkginstall: Not overwriting files owned by other packages: zope3: /usr/lib/python2.5/site-packages/ZConfig/__init__.py zope3: /usr/lib/python2.5/site-packages/ZConfig/cfgparser.py adding Conflicts: zope3 to ZConfig should be enough, I have added that to the package svn in the pkg-zope repository (http://lists.alioth.debian.org/pipermail/pkg-zope- developers/2009-November/005668.html). -- package python-zconfig 2.7.1-1 failed to install/upgrade: https://bugs.launchpad.net/bugs/487536 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185418] Re: reports its version number in .egg-info as 0.0.0
Was a packaging artifact, never affected upstream zope.interface. Anyway, has been fixed for a long time. ** Changed in: zope.interface Status: New = Invalid -- reports its version number in .egg-info as 0.0.0 https://bugs.launchpad.net/bugs/185418 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250751] Re: Could not calculate the upgrade: Resolve generated breaks, this may be caused by held packages
From the dates, I'm assuming seems that my fixes were the problem. But, I can't reproduce the the bug. -- Could not calculate the upgrade: Resolve generated breaks, this may be caused by held packages https://bugs.launchpad.net/bugs/250751 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185418] Re: reports its version number in .egg-info as 0.0.0
Could we try building zope.interface from the zope.interface tarball instead of from the zope3 tarball? This is exactly what I suggested. There is such a package (along with a lot of other zope.* packages) in the schooltool PPA (deb-src http://ppa.launchpad.net/schooltool- owners/ubuntu gutsy main). Unfortunately it is deficient in quite a few ways (no debug info, no copyright info). I really would love to help out in this, but simply do not have the time for the next month or so. -- reports its version number in .egg-info as 0.0.0 https://bugs.launchpad.net/bugs/185418 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185418] Re: reports its version number in .egg-info as 0.0.0
I'd suggest patch the zope3 source package to not create python- zopeinterface binary package. Instead just throw the zope.interface code away when building zope3. Then make a new source package, based around the zope.interface tarball that provides python-zopeinterface in some way. Then the old zope3 monstrosity will depend on python-zopeinterface (as it now does). Finally, the fun part is to try make sure you don't break the zope3 tarball when there is version skew between zope.interface and zope3. I'd suggest trying to integrate the zope3 tests into the autopkgtest framerwork. (I'm not sure if the 3.3 tests run properly on a read-only directory, which is a problem you will encounter, but I did get some patches in 3.4) -- reports its version number in .egg-info as 0.0.0 https://bugs.launchpad.net/bugs/185418 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185418] Re: reports its version number in .egg-info as 0.0.0
** Also affects: zope3 (Ubuntu) Importance: Undecided Status: New -- reports its version number in .egg-info as 0.0.0 https://bugs.launchpad.net/bugs/185418 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185418] Re: reports its version number in .egg-info as 0.0.0
This isn't really a bug in zope.interface. It's a packaging bug of some kind. I've assigned it to the ubuntu zope3 package as it obviously affects that. The package in ubuntu is built using the Zope3 monolithic tarball (using zpkg!!!). This smells like a bad interaction between setuptools and zpkg in the install.py of that tarball. One way of side-stepping this bug is to build the python-zopeinterface package directly from it's tarball at http://pypi.python.org/pypi/zope.interface which should sidestep this problem and others like it. i.e. basically split it out of the zope3 package. -- reports its version number in .egg-info as 0.0.0 https://bugs.launchpad.net/bugs/185418 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
