William Stein wrote: > Note that you could also submit a patch to Sage with the code you're > doctesting. > I did that with all the tests from both of the books I published, and > I encourage you and many others to do the same with the code from your > article. The code would go in a file > > devel/sage/sage/tests/ > > like the file devel/sage/sage/tests/book_stein_modform.py > > In fact, I could imagine having dozens of files in that directory, and > when doctests break there, we could notify the authors before > releasing the version of Sage that breaks their doctests for feedback > -- then they could update their papers or Sage. Maybe this is how > the technical aspect of jsage should work: > http://www.sagemath.org/library/jsage/index.html >
Also, such code could be loaded into a running Sage session easily, something like the contributions directory of maxima. Personally, I would love if our special-purpose code (probably too specialized to be included in Sage) were accessible to anyone that had Sage. Thanks, Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
