I think that after a certain point, the best way to get experience with Sage _is_ to submit a patch. There are lots of little things to learn when you do that, and they all help you understand the system better (this is my experience anyway). When your patch is reviewed you will probably learn more of the details of the Sage coding and documentation conventions. That had the effect on me of making me code more in the 'official' Sage style even when I'm working on something I don't plan on submitting, which was a good influence and makes it easier to prepare stuff for submission in the future.
If you are wrestling with the little details of submission, the IRC sage-devel channel is a good place to get instant help. -M. Hampton On Oct 17, 6:11 am, Stan Schymanski <[EMAIL PROTECTED]> wrote: > Hi David, > > Thanks for the reply. I think it would be much more elegant to have a > recursive option in the current subs method. Would this be worth a ticket? > I'll need a lot more experience with Sage before I start submitting > patches, but thanks for pointing me to the Programming guide. I forgot > about that. > > Cheers > Stan > > David Joyner wrote: > > Would it be better to add a method="recursive" option to the current > > subs method? > > > To answer your question though, I think the procedure to add anything > > to Sage is to create a patch and submit it to trac. See the > > Programming guide for > > some hints. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
