On Jan 13, 2009, at 12:54 PM, Vincent Delecroix wrote:
>
> Jason was right : "I have some python code that creates some objects
> that are interesting to me; how do I get this into Sage
> permanently ?". I've aldready put my files in the $SAGE_ROOT/devel/
> sage/sage directory and I've done two modifications of the
> configuration files (right ones ?) :
> in $SAGE_ROOT/devel/sage/sage/all.py : I had the line " from
> sage.my_module import * "
> in $SAGE_ROOT/devel/sage/setup.py : I had the 'sage.my_module' in
> the package list
>
> The problem is that doesn't work (my library is not visible from
> sage).
Did you run "sage -b" to build your changes?
> The project is in developpement version but some people could like to
> use it right now. So I think that a spkg is, during the developpement
> version at least, a better option.
An spkg is (probably) much heavier weight than what you need--you'd
have to write an install/build script and repeatedly package/post it.
It's also much harder to get people to actually use (and review) your
changes as the Sage workflow is built around patches.
We use the mercurial revision control system, so when you are happy
with your changes, do
sage: hg_sage.commit("some comment describing your code here")
sage: hg_sage.export("tip", "/path/to/where/you/want/to/save/the/
changes.patch")
then create a ticket on http://trac.sagemath.org/sage_trac and attach
the patch file you created above.
- Robert
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
