On Apr 17, 8:49 am, John Cremona <john.crem...@gmail.com> wrote: > > I think I took care of it in #5808 -- take a quick look if you have a > > chance. > > No, after applying #5808 there are still two lines in that file (55 > and 204) containing "..link::" which should be ".. link::", I think. > Though I do not know what the link directive actually is.
OK, the bit of the Sage Developer Guide at the very end of http://www.sagemath.org/doc/developer/conventions.html#documentation-strings shows it with a space. The purpose is to let a portion of a Sage session continue along, but add some commentary in between the "sage:" input/output. I may have missed it somewhere but is there a command to build/test docstrings on just a single file for (a) warnings and errors (b) final formatted appearance I'm thinking of the functionality of sage -b and sage -t on a per- file basis, but relative to documentation. I was flying blind on some of the docstrings I wrote where I was trying to use some of the ReST commands. Maybe John P's work to "pretty print" docstrings in the notebook is the solution. Rob --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
