On 21/01/2013 09:39, Philippe Ombredanne wrote:
On Sat, Jan 19, 2013 at 11:54 PM, Chris Withers<chris@simplistix.co.uk> wrote:
On 19/01/2013 21:16, Jim Fulton wrote:
Another option would be to pin setuptools in your buildout.cfg to avoid the upgrade. Just a note to say that this didn't work: http://jenkins.simplistix.co.uk/job/testfixtures-buildout/PYTHON=2.7,label=w... The problem is that bootstrap.py *always* dowloads setuptools. I wish it didn't do that if the right version of setuptools was already in the egg cache...
You could try to pin the distribute or setuptools version used by bootstrap this way: python bootstrap.py --version 1.7.0 \ --distribute --setup-source=<path to script>/ez_setup.py \<-- saved locally --download-base=<path to download-cache>/dist/<-- with a saved locally version of setuptools
Given the only reason I was trying to pin setuptools was to try and workaround the windows problem the subject of this message pertains to, I don't really want to do all the hacks above. Just taking the pinned version out worked for me, which is fine since it didn't help the windows situation anyway... Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk