Opened at 2007-09-21T21:27:47Z
Closed at 2008-06-02T16:56:42Z
#140 closed defect (wontfix)
the "setuptools+GNU stow" hack doesn't work on zope.interface
Reported by: | zooko | Owned by: | zooko |
---|---|---|---|
Priority: | minor | Milestone: | undecided |
Component: | packaging | Version: | 0.7.0 |
Keywords: | Cc: | ||
Launchpad Bug: |
Description (last modified by zooko)
The trick of
${PYTHON:-python} ./setup.py install --single-version-externally-managed --record=`${CYGPATH} ${PKG_DIR}/${PKG_NAME}-install.log` --prefix=`${CYGPATH} ${PKG_DIR}`
Which can be used to install setuptools packages in a GNUstow-compatible way doesn't work with zope.interface. I don't know why the zope.interface module is not loadable afterward. We don't actually rely on this trick officially -- it isn't described in much detail in the README, and the web page describing it: SetuptoolsAndGNUStow? -- isn't complete yet.
Change History (13)
comment:1 Changed at 2007-09-21T21:28:04Z by zooko
- Description modified (diff)
comment:2 Changed at 2007-09-26T21:17:48Z by zooko
- Status changed from new to assigned
comment:3 Changed at 2007-09-26T21:39:22Z by zooko
No, it wasn't a mistake on my part. The aforementioned bug in the zope.interface setup.py merely makes it harder to notice if your problem is that you don't have setuptools installed.
However, even if you use setuptools to install zope.interface, then it still fails if you install it with the SVEM hack. The proximate cause of failure is that the resulting "zope" directory, which has an "interface" subdirectory, doesn't have an "init.py" file. If you run "touch ${PREFIX}/zope/init.py" then this fixes it and after that you can import zope.interface.
comment:4 Changed at 2007-09-28T02:28:10Z by warner
- Component changed from unknown to packaging
comment:5 Changed at 2007-10-01T21:03:04Z by zooko
I submitted a bug report to the distutils-sig mailing list.
comment:6 Changed at 2007-10-02T20:32:22Z by zooko
setuptools can't install init.py's for namespace packages when --single-version-externally-managed
http://mail.python.org/pipermail/distutils-sig/2007-October/008333.html
comment:7 Changed at 2007-10-02T20:56:48Z by zooko
- Milestone changed from 0.6.1 to 0.7.0
- Version changed from 0.5.1 to 0.6.0
This issue needs to be documented on the setuptools and GNU stow page?.
But not necessarily for v0.6.1 release...
comment:8 Changed at 2007-11-01T19:36:33Z by zooko
We're focussing on an imminent v0.7.0 (see the roadmap) which hopefully has #197 -- Small Distributed Mutable Files and also a fix for #199 -- bad SHA-256. So I'm bumping less urgent tickets to v0.7.1.
comment:9 Changed at 2007-11-01T19:36:38Z by zooko
- Milestone changed from 0.7.0 to 0.7.1
comment:10 Changed at 2007-11-13T18:32:14Z by zooko
- Milestone changed from 0.7.1 to 0.7.2
- Version changed from 0.6.0 to 0.7.0
comment:11 Changed at 2008-01-23T04:21:47Z by zooko
- Milestone changed from 0.7.2 to undecided
comment:12 Changed at 2008-06-01T20:47:33Z by warner
- Milestone changed from eventually to undecided
comment:13 Changed at 2008-06-02T16:56:42Z by zooko
- Resolution set to wontfix
- Status changed from assigned to closed
This is no longer really essential for Tahoe installation use cases.
I think the problem is actually a combination of a mistake on my part and some silly behavior on the part of the zope.interface setup.py script:
https://bugs.launchpad.net/zope3/+bug/145374