On Mon, Mar 24, 2008 at 8:33 PM, Floris Bruynooghe
[EMAIL PROTECTED] wrote:
Something that this requirement should probably explicitly describe:
does this database only concern modules, i.e. installed in a directory
that's on sys.path? My understanding is that it does. However I'm
unsure
Folks:
Here is a simple proposal: make the standard Python import
mechanism notice eggs on the PYTHONPATH and insert them (into the
*same* location) on the sys.path.
This eliminates the #1 problem with eggs -- that they don't easily
work when installing them into places other than your
Bug report #1:
_get_unpatched() returns a module from the system site-packages
instead of the module from the PYTHONPATH which ought to have
precedence, leading to setuptools-0.6c8 invoking setuptools-0.6a9 in
the following stack trace:
At 06:09 PM 3/26/2008 -0700, zooko wrote:
Bug report #1:
...
PYTHONPATH=/home/buildslave/slave-tahoe/dapper/build/support/lib/
python2.4/site-packages python ./setup.py develop --prefix=/home/
buildslave/slave-tahoe/dapper/build/support
...
Running Nevow-0.9.18/setup.py -q bdist_egg --dist-dir
zooko wrote:
Folks:
Here is a simple proposal: make the standard Python import
mechanism notice eggs on the PYTHONPATH and insert them (into the
*same* location) on the sys.path.
This eliminates the #1 problem with eggs -- that they don't easily
work when installing them into
At 07:25 PM 3/26/2008 -0700, zooko wrote:
On Mar 26, 2008, at 6:56 PM, Phillip J. Eby wrote:
https://dev.allmydata.com/buildbot-tahoe/builders/dapper/builds/
1427/steps/compile/logs/stdio
That URL requires login credentials that I don't have. And I need
the rest of the traceback to make any
