Simon King wrote: > Dear Vincent, > > On Jan 13, 6:38 pm, Vincent Delecroix <20100.delecr...@gmail.com> > wrote: >> I need objects in Sage that not yet totally exist (a combinatoric one, >> and another derived from oriented graph). So I write some python files >> (pure python for the moment) to create those new objects. My problem >> is that I didn't find any place on the web where it's said how to >> construct a spkg file from my python files and how can I integrate my >> objects in sage. > > Is your question 'How do I use my python files in Sage'? > As stated in the other replies, you don't need to produce an spkg. > Simply start sage, and, assuming your file is called foo.py, do > sage: from foo import * > or > sage: attach foo.py > or > sage: load foo.py > > Or is your question 'I can use my foo.py in Sage -- but still I want > to make it an spkg'? > But then, why do you want? AFAIK, the creation of an spkg only makes > sense if you have various python and cython modules that also rely on > C or Lisp or Fortran code, perhaps involve some executables etc. > > Anyway, the creation of an spkg is explained in the Sage Developer's > Guide at http://modular.math.washington.edu/sage/doc/prog/node45.html > > Or is your question 'Technically I am able to produce an spkg; but > what can I do in order to make it part of the Sage distribution'? > * AFAIK, you need to open a trac ticket (see > http://modular.math.washington.edu/sage/doc/prog/node47.html ), > describe your package in the ticket and give evidence why it should be > distributed. Perhaps you also point sage-devel to the ticket. > * Then, several people will review your package, and if it gets > positive review, it may become an optional Sage package. > * If it turns out that the package adds something that many people > need then it may eventually become a standard Sage package.
Or is your question, "I have some python code that creates some objects that are interesting to me; how do I get this into Sage permanently?"? In that case, it may be best to contribute the code directly to Sage, in the sage library, instead of creating an extra spkg that has to be installed separately. You can do this by adding it to the sage source (in $SAGE_ROOT/devel/sage/sage) in the appropriate place, possibly modifying some configuration files that load things properly, creating a patch, and posting that to a trac ticket (and maybe also posting a message to sage-devel describing the code and asking for reviews). So what would you like to do? What does your code do? Can you post it anywhere? Thanks, Jason --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
