NOTE: cc'ing distutils-sig for help debugging potential problem with setuptools on gentoo.


Hans Meine wrote: 
Am Donnerstag, 10. April 2008 09:19:31 schrieb Hans Meine:
  
The same errors occur without virtualenv, so you're obviously right that
this is setuptools-related.  I could try again and really deinstall
Gentoo's setuptools (instead of just locally installing it the official
way), but I really doubt now that this would make a difference.
    

So, I have even tried this - deinstalling setuptools altogether, and 
installing everything from scratch.  I used "script" to create a log file of 
the process with all input and resulting output + errors:
http://kogs-www.informatik.uni-hamburg.de/~meine/clean-ets-install.log

Thanks for providing that full log!   From looking at that, I'm really starting to suspect a bug in setuptools 0.6c8 as I can't make any sense of the following sequence of events.  While it's possible we've done something wrong in our setup.py scripts, I have my doubts as this release appears to install fine for users on Windows, OSX, and RH.  (For distutils-sig readers, Hans is using Gentoo.)

1) During the first install attempt of "ets", the log shows two lines reporting success with installing enthought.tvtk-2.0.2-py2.4-linux-i686.egg.  One right after downloading and building enthought.tvtk from the source tarball, and one in the middle of the enthought.kiva build.

2) Regarding that enthought.kiva build, the log indicates that a dependency caused a search to be made for "enthought.kiva>=2.0.3.dev,<=2.0.3" and a match was found (enthought.kiva-2.0.3.tar.gz)  The log then shows this building, apparently a successful build (no error messages, just warnings) up until the normally reported "Installed /path/to/egg" line where it mentions success with installing enthought.tvtk rather enthought.kiva.  After that, it reports being unable to find the enthought.kiva distribution.

3) You then re-run the "easy_install -f ... ets" command which has no problem building enthought.kiva this time using the exact same source tarball.


I have no idea what might be causing this sequence of events.   Has anyone seen anything similar with setuptools?


-- Dave