The error that Michael A reported seems to have the space in it, but I
believe I used the ..link construction somewhere else in that file
(its on my home machine) and it didn't raise an error, and probably it
didn't have a space?

It would be nice to do the right thing (whatever that is), but if it
were removed I guess the short comments will just get formatted
verbatim, which is not the end of the world.  So I guess whatever
works (do it right, or drop it) is fine by me.

I can experiment some on Saturday if you'd rather wash your hands of
it.  ;-)

Rob

On Apr 17, 2:24 pm, John H Palmieri <jhpalmier...@gmail.com> wrote:
> On Apr 17, 1:43 pm, Rob Beezer <goo...@beezer.cotse.net> wrote:
>
>
>
> > 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-...
>
> > 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.
>
> You're right, and it seems from reading the source code for 'sage-
> doctest' that a space is required. Anyway, I tried removing the entire
> string "..link::" from sudoko.py, and it passes tests like that, so
> maybe we don' t need it there at all.  Should I revise the patch at
> #5808 making that change?
>
>   John
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to