On 06-04-13 02:55, Chris Withers wrote:
Having bootstrap.py really make sure things are started again from
scratch would likely solve all these problems. (The .installed.cfg stuff
I remember hitting before, when only using clean pythons)
Removing .installed.cfg: not sure. Some recipes fail when
On 05/04/2013 13:16, Jim Fulton wrote:
The non-develop eggs here have significantly *lower* version numbers.
(and really, if I say I'm developing a package, why would a non-development
version be picked?!)
There are people who agree with you and people who don't.
What's your view on it?
My t
On Fri, Apr 5, 2013 at 12:01 PM, Chris Withers wrote:
> On 05/04/2013 12:48, Jim Fulton wrote:
>>>
>>> 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.
>
>
> Entho
On 05/04/2013 12:48, Jim Fulton wrote:
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.
Enthought Python Distribution, I should emphasise *was* using above...
Since that
On Fri, Apr 5, 2013 at 11:36 AM, Chris Withers 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 dou
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
