Done, and it works.... But now I wonder how to build the patch, as SAGE/DATA is not monitored.. :-)
I could also just attach it to the Trac ticket, and let it be merged to Sage, as it does not seem worth building a spkg.... Nathann On Aug 22, 12:25 pm, William Stein <wst...@gmail.com> wrote: > On Sat, Aug 22, 2009 at 1:56 AM, Simon King <simon.k...@nuigalway.ie> wrote: > > > Hi! > > > On 22 Aug., 10:11, Nathann Cohen <nathann.co...@gmail.com> wrote: > > > Is there a variable defining the path of sage up to the current > > > branch ? > > > There is SAGE_ROOT, and if I am not mistaken then SAGE_ROOT+'/devel/ > > sage/' is a link to the current mercurial branch. > > > But there is also a folder SAGE_ROOT+'/local/'. Your package could > > create a sub-folder (this is what distutils would do for local data of > > a package, IIRC) and store all its data in that sub-folder. > > No, use the SAGE_DATA variable, which is defined in misc/misc.py: > > sage: sage.misc.misc.SAGE_DATA > > '/Users/wstein/sage/build/64bit/sage/data/' > > Your graph should go somewhere in SAGE_ROOT/data/something... > > William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an 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 -~----------~----~----~----~------~----~------~--~---
