On 05/04/2013 12:14, Marius Gedminas wrote:
Any help here would be very gratefully received...
Workaround #1: run 'bin/buildout -N' so it won't try to upgrade
distribute.
I just pinned distribute in the buildout.cfg, as I showed, saves
forgetting to pass -N later.
Workaround #2: always always always wrap your buildouts in a virtualenv.
How would this have helped here? The python2.6 I ran bootstrap with is
totally clean, compiled by me...
I started using a 'virtual-bootstrap' script that does
#!/bin/sh
rm -rf develop-eggs .installed.cfg python
virtualenv --distribute python
python/bin/python bootstrap.py
bin/buildout "$@"
and haven't encountered any issues yet.
My problem is that I *want* to use that python2.7 as a base for a lot of
my projects. I absolutely don't want to be trying to compile numpy/etc
on a Mac when I'm already paying Enthought to do that for me ;-)
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
