On May 19, 12:03 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > Hehe, it is good to share the blame. I meant had I know that this > issue causes this much trouble I would have attempted to do 3.0.2 > quicker instead of the two week cycle. Is there any way to test Cython > introspection automatically via the standard doctests, so that we > could catch such an issue via the normal doctesting? It would also be > interesting to see if once we have the XMLRPC stuff in place [I think > we do already] to run some tests via the commandline by "injecting" > content into some worksheet so that we do more automated testing.
It's also possible to doctest the Sage command line (to some extent) using sage/interfaces/sage0.py. In sage/misc/randstate.pyx, search for "subsage" to see an example of this technique. Carl --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
