-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pascal Peregrina wrote:
Again, if you read my hack in my initial mail, you'll see that the issue is with the python path (I run make in a temporary "build" directory and the untared Zope source is elsewhere)... So no, my source file is NOT corrupted...
Let me explain again. In setup.py there is this (nasty) code: sys.path.insert(0, 'inst') import versions del sys.path[0]
In my case, this fails because the "inst" directory is not a subdirectory of my temporary "build" directory.
So if I fix the path to "inst" with this in setup.py (I copy/pasted this code from one of my own python scripts):
try: MAKEFILEDIR = os.path.dirname(os.path.abspath(__file__)) except: MAKEFILEDIR = os.path.dirname(os.path.abspath(sys.argv[0])) sys.path.insert(0, '%s/inst'%MAKEFILEDIR) import versions del sys.path[0]
...it works fine.
Does it make sense now?
This (nasty) code in setup.py does not exist in Zope 2.8.4
I fixed out-of-tree builds recently (I can reproduce your error on a 2.9.4 tarball, but not with the 2.9 branch): http://svn.zope.org/Zope/branches/2.9/setup.py?rev=69978&r1=69111&r2=69978 http://svn.zope.org/Zope/branches/2.10/setup.py?rev=69979&r1=69113&r2=69979 It looks as though I forgot to port that fix to the trunk, however. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFEozV+gerLs4ltQ4RAhYIAJkBFc8ixYwFkWTL2sorShmSSx4VqwCfcgva 5ApsUtRT6pSMG7J5i+dWkiM= =+j94 -----END PGP SIGNATURE-----