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 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.
In that case this information may help: http://docs.python.org/install/index.html#distutils-configuration-files It looks like checking for .pydistutils.cfg (and the equivalent on windows) should cover it since the system distutils.cfg won't clash with the sage python. cheers, prabhu --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
