David Glick <[email protected]> writes:
> On 1/16/12 6:45 PM, Ross Patterson wrote:
>> Unfortunately, I haven't been able to get a clean test environment for
>> the life of me. I'm using a clean Python 2.7 build from source, turning
>> everything in ~/.buildout/default.cfg off, and running tests in a clean
>> checkout of the zc.buildout/trunk buildout. Even under those conditions
>> I get 17 failing tests before any changes. With this environments
>> cache, I see 41 failures, but I can't make sense of it. This patch
>> yields another 2-3 fold decrease to 6 seconds for the same buildout and
>> is driven by profiling data, not guessing. Can someone help me get this
>> patch in?
>>
>>
> See DEVELOPERS.txt in the zc.buildout source for how to get a working
> test setup. In particular you need to run dev.py using a Python
> without setuptools present, and you need to have python2.5 available
> on your path.
Thanks for this tip and, as I said on freenode, sorry for not RTFMing.
To get this working i had to do completely separate Python 2.6 and 2.5
builds from source like so:
$ ./configure --prefix=~/src/zc.buildout && make && make install
That way my zc.buildout checkout is it's *own* python installation of
two versions. With this and the differences in DEVELOPERS.txt, I now
have all tests passing on trunk. Yay! Now I'm looking into the
failures on my branch.
FYI, I also tried doing:
$ virtualenv -p ~/src/buildout.python/python-2.6/bin/python2.6
--no-site-packages --distribute --clear .
...for both Python 2.5 and 2.6 and then deleting the distribute egg from
lib/python2.#/site-packages but even that resulted in test failures.
Not sure if this indicates a problem with the way buildout.python builds
python.
Ross
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
