On Aug 23, 7:55 am, Chris Seberino <cseber...@gmail.com> wrote: > So what is the next step to move forward?
Open a ticket, implement a solution and attach a patch to the ticket. See the developer guide http://www.sagemath.org/doc/developer/index.html for an outline. It is probably instructive to link back to this thread on the ticket for documentation. Note that once you have a patch that works for you, you have at least solved the problem *for yourself*. It's nice if it gets included into Sage eventually, but reviews can take a long time. I am not sure how many people consider the feature you are proposing a high priority. It will give you a good feel for how the process works and a much better familiarity with the Sage code base, though, which will be invaluable for further use of and work on Sage. -- 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 URL: http://www.sagemath.org
