Can you have a look at http://patchbot.sagemath.org/ticket/14266/
There are two tickets to test. I commented "apply ticketA ticketB" but now only ticketB is seen by the patchbot server. On Friday, May 17, 2013 9:00:40 AM UTC+1, Robert Bradshaw wrote: > > Yeah, I realized this morning this plugin was broken, as "..." matches > any three characters (of course). I'm planning on releasing 1.3.1 > soon, but want to do some more testing first. > > On Fri, May 17, 2013 at 12:58 AM, Frédéric Chapoton > <fchap...@gmail.com <javascript:>> wrote: > > Hello, > > > > I do not understand what the new plugin "plugins.doctest_continuation" > is > > supposed to test. > > Is it the plugin alluded to in the previous post ? Is this documented on > the > > web somewhere ? > > > > Anyway, the plugin fails on the patch for > > http://trac.sagemath.org/sage_trac/ticket/12848 > > > > but this patch does not contain any '''...''' ! > > > > Le jeudi 9 mai 2013 02:07:57 UTC+2, Robert Bradshaw a écrit : > >> > >> On Wed, May 8, 2013 at 2:58 AM, Jeroen Demeyer <jdem...@cage.ugent.be> > >> wrote: > >> > The new doctesting framework allows doctests with continuation to be > >> > written > >> > like > >> > > >> > sage: > >> > ....: > >> > ....: > >> > > >> > instead of the old > >> > > >> > sage: > >> > ... > >> > ... > >> > > >> > The new syntax is much better because it has correct alignment and it > >> > would > >> > allow expected output to start with ... if we disallow the old > syntax. > >> > It is > >> > also the syntax that one sees in the IPython command line. > >> > > >> > The problem is that people will keep adding doctests in the old > style. > >> > So I > >> > am thinking about ways to help the transition of ... to ....: > >> > > >> > The following is an idea I am inclined to try: > >> > > >> > Automatically replace replace ... to ....: in newly added/changed > >> > doctests? > >> > This can be done with some sed magic when merging the patch. And > >> > moreover, > >> > it could even be done in a way to avoid merge conflicts (if patch A > adds > >> > a > >> > ... doctest and patch B changes that ... doctest, I can handle that). > >> > The > >> > main disadvantage here is that patches on Trac will not match the > >> > actually > >> > merged patches. I am even thinking about having 2 branches in the > >> > Mercurial > >> > repository, one with the patches as on Trac and one with the doctests > >> > changed (the latter one being the "official" master branch). > >> > >> I don't see the merits of having two branches. Also, if its entirely > >> transparent, people won't know to change. I can add a plugin that > >> fails on the old-style continuation which would be really easy--it > >> wouldn't be required at this point but I bet people would happily > >> migrate to it (if not for that patch, for all subsequent work). > >> > >> - Robert > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "sage-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to sage-devel+...@googlegroups.com <javascript:>. > > To post to this group, send email to > > sage-...@googlegroups.com<javascript:>. > > > Visit this group at http://groups.google.com/group/sage-devel?hl=en. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
