#13610: Make sage -t --debug trigger on an incorrect doctest in addition to an
unexpected error
-----------------------------------------------------------------------------------------------+
Reporter: roed
| Owner: mvngu
Type: enhancement
| Status: new
Priority: major
| Milestone: sage-5.5
Component: doctest
| Keywords:
Work issues: keyboard interrupt, doctesting after exiting the debugger not
working correctly | Report Upstream: N/A
Reviewers:
| Authors: David Roe
Merged in:
| Dependencies: #12415
Stopgaps:
|
-----------------------------------------------------------------------------------------------+
#12415 introduces the ability to drop into a Python debugger when an
unexpected error is encountered. I was attempting to have a similar
behavior happen when an incorrect result was obtained so that it's easier
to figure out what has gone wrong in the doctest. But problems with
interrupt handling were delaying the completion of #12415 (already a
patchbomb), so I've stripped out that functionality and put it here.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13610>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.