Hi Soroosh, On Jan 22, 6:14 pm, "Soroosh Yazdani" <[EMAIL PROTECTED]> wrote: > On Jan 21, 2008 5:00 PM, mabshoff < > > [EMAIL PROTECTED]> wrote: > > > Hi Soroosh, > > Hi Michael, > > > > > Hmm, I think there is a problem when building the extensions since you > > will need to have write permissions to copy the resulting dynamic > > library over. That could be potentially avoided by having the Sage > > python directory in there too, but I am not quite sure how much work > > needs to be done to make that possible. <snip> > > hmm, why do I need write permission in that directory? Naively, I don't see > when sage needs to write to that directory, so I'm curious. > Actually I am not a python expert but that brings a question to me. Python usually put its modules/libraries in a location defined by either PYTHONHOME or PYTHONPATH and one of the things sage do is set PYTHONPATH so as to only see its own version of python. Now I am wondering if we can tell python to look for modules in several location in order, like you can with executables for example with the PATH variable. In this case you wouldn't have to copy over all the python directory but just put new stuff overriding or supplementing sage one in a defined directory, say $HOME/.sage/python/ . Also as it stand the sage python directory on my home machine is 700MB while modern hard drive can laugh at it, the "antique" I am writing this on would not appreciate very much the copying over.
Furthermore being able to do this, means that I can start touching python packages in sage without having to do everyone of them at once. Cheers, Francois --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
