On May 2, 1:25 am, Prabhu Ramachandran <[email protected]> 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 will affect
> any new spkg installs also since distutils will always pick it up.
> There is a Python issue for this too:
>
> http://bugs.python.org/issue1180
Thanks for the link - I should really get on the python list where all
the bugs are CCed :)
> 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 work.
Yeah, looking at the patch I would prefer to just warn the user and
tell him/her to move the file out of the way. The patches at that
ticket you quote all seem invasive and I don't want to touch every
python based spkg in Sage. Another thing is that if someone wants to
run
./sage -sh
python setup.py install
manually it would still be broken. So sticking the test somewhere in
sage-env might be a good idea.
> cheers,
> prabhu
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
