[Distutils] [buildout] weird behaviour with system-installed packages and cross-buildout contamination

[Reinout van Rees]

On 13-02-13 10:15, Chris Withers wrote:
> You're ignoring these lines in setup.py:
>
> https://github.com/Simplistix/testfixtures/blob/py3k/setup.py#L16

You're right, I missed that part.

I tried your buildout with a 2.0 bootstrap and I did get a bin/nosetests.


I also made a virtualenv and pip-installed nose into that and then ran 
the buildout: buildout downloaded its own copy.

Buildout doesn't isolate you from the system python, but that does not 
mean it searches the system packages for eggs to use. (You need 
something like http://pypi.python.org/pypi/syseggrecipe to explicitly 
grab a system egg).


My guess is that the .installed.cfg somehow interferes. I've never 
really trusted that one and I never looked into how it worked. If 
something unexplainable happens, I often blow this file away and start 
again.

Chris, does it work for you if you start from scratch in an empty dir?
Your jenkins output seems to suggest that you let jenkins create a fresh 
empty dir for you, so it *should* work...


(Unrelated: you're using nose-cov; I can now get a similar coverage 
output out of nose itself, so the nose-cov functionality is probably 
included in recent nose releases. Great to get that coverage feedback 
right in your face after running the tests :-) )

Reinout

-- 
Reinout van Rees                    http://reinout.vanrees.org/
reinout at vanrees.org             http://www.nelen-schuurmans.nl/
"If you're not sure what to do, make something. -- Paul Graham"