mabshoff wrote:
>> So one option would be to backport the patch to the Python version you
>> ship and always invoke setup.py such that it ignores the
>> .pydistutils.cfg. Of course, a simple test script that looks for the
>> file and warns the user (like the macports warning/error) would also wor
On May 2, 1:25 am, Prabhu Ramachandran wrote:
> mabshoff wrote:
> >> I think this should be documented somewhere so others don't fall into
> >> the same trap. Thanks.
Hi,
> > Cool. Thanks for telling us - I have made this #5961.
>
> Glad to be of some assistance. BTW, the .pydistutils.cfg w
mabshoff wrote:
>> I think this should be documented somewhere so others don't fall into
>> the same trap. Thanks.
>
> Cool. Thanks for telling us - I have made this #5961.
Glad to be of some assistance. BTW, the .pydistutils.cfg will affect
any new spkg installs also since distutils will alw
On May 1, 7:32 pm, Prabhu Ramachandran wrote:
> Dear Sage developers,
Hi Prabhu,
> I tried to build Sage-3.4 on my intel macbook (Mac OS X 10.4.11). I
> have Xcode 2.5 installed and gcc-4.0.1. I downloaded the sage-3.4.tar,
> untarred it and ran make. I have macports installed so changed the
