On Mon, Oct 5, 2009 at 10:08 AM, Robert Bradshaw < rober...@math.washington.edu> wrote:
> > On Oct 5, 2009, at 8:51 AM, kcrisman wrote: > > >>> Okay, so there was no official resolution after all. Also note the > >>> most recent comment on #6572. Thanks! > >> > >> There is now a new patch up at #6572 which should allow double colons > >> at the end of lines, not just on blank lines. I think this patch is > >> important, because right now a bunch of doctests in the documentation > >> are not actually being run, and indeed a number of them fail when you > >> do run them: our current documentation is actually wrong in a number > >> of places! Should this be a blocker? > >> > >> One of the patches at #6572 depends on #6642, so someone needs to > >> review that one. (Not you, kcrisman, since you wrote the patch.) > > > > > > Yes, I realize that :) Also note that I don't guarantee #6642 doesn't > > break something obscure - only that it's a step in the right direction > > for getting our solve code shipshape, which several other open tickets > > also complain about. There is also a typo in line 5436 of the patch > > on #6642 (approximate is spelled wrong). > > Why are we using double-colons to pick up doctests at all, shouldn't > we just search for lines starting with "sage:" double-colons are just > for ReST (where I think they're highly redundant as well). > > This is not only used to pickup doctests but for syntax highlighting and for constructing live worksheets out of the documentation. William --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
