id summary reporter owner description type status priority milestone component resolution keywords cc merged author reviewer upstream work_issues branch commit dependencies stopgaps
1866 [probably fixed] bug in doctesting -- long time not respected in some contexts was failure "{{{
On Jan 20, 2008 7:28 AM, Lars Fischer <> wrote:
>
> Hello,
>
> I think I have found a bug:
> chapter 2.4.1 of the Programming guide states, that comments like ""#
> long time (!)"" prevents the example from being tested.
Yep, that is a bug. I've made it.
>
> But:
> sage -t quadratic-modules.sage
> sage -t quadratic-modules.sage
> Example 13 (line 433)
> TIMEOUT!!
> IN:
> phi.level()
> phi = fqmodule([11,33]);
> phi.tau_invariant()
> phi = fqmodule([11,33]); # long time (!)
> phi.sigma_invariant() # long time (!)
> OUT:
>
>
> This applies to sage 2.10.
>
> I think the reason is:
> sage -t calls
> sage-sage and then
> sage-test, which in turns calls
> sage-doctest_tex, if extension is "".sage"" instead of sage-doctest.
>
> At least sage-doctest looks for ""long time"" inside comment_modifiers()
> and sage-doctest_tex doesnot.
>
> With best regards,
> Lars Fischer
}}}
My first thought on reading the above is ""get rid of handling .sage files in a special way in order to automatically fix all such issues"". That's what I did with .tex files a while ago. " defect closed major sage-duplicate/invalid/wontfix doctest coverage invalid mjo N/A