On Fri, Apr 5, 2013 at 11:36 AM, Chris Withers <ch...@python.org> wrote: > On 05/04/2013 12:15, Marius Gedminas wrote: >> >> Check develop-eggs/, there may be a distribute.egg-link file that puts >> >> /Library/Frameworks/EPD64.framework/Versions/7.3/lib/python2.7/site-packages >> in your sys.path. >> >> When in doubt, rm -rf develop-eggs before retrying. > > > Well, this worked. > > My guess as to what happened: I was using python2.7 (which is EPD, > containing a tonne of packages including an older version of xlrd).
BTW, I have no idea what EPD means. > > Since that xlrd was getting picked instead of the one in the develop line > (wasn't that bug supposed to be fixed in buildout 2?!) There was quite a bit of discussion about this recently and there was no consensus that develop eggs should be preferred to over non-develop eggs with higher versions. > I switched to > python2.6, which I knew was clean. > > It sounds like I should have had the prescience (!) to do: > > rm -rf develop-eggs/ .installed.cfg > > ...before I did: > > python2.6 bootstrap.py > > *sigh* > > At times like this (when I've just wasted 1.5hrs chasing my tail) I really > truly hate buildout :-( It's times like this that I really really hate it when people insist on using dirty Pythons when they should know better. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
