Make sage -t --debug trigger on an incorrect doctest in addition to an unexpected error
#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.
Change History (14)
| Dependencies: |
#12415 →
#14289
|
| Dependencies: |
#14289 →
#14289, #14290
|
| Status: |
new →
needs_review
|
| Component: |
doctest →
doctest framework
|
| Dependencies: |
#14289, #14290 →
#14289, #14290, #14331, #13278, #14370
|
| Status: |
needs_review →
needs_work
|
| Reviewers: |
→ Jeroen Demeyer
|
| Status: |
needs_work →
needs_review
|
| Status: |
needs_review →
positive_review
|
| Work issues: |
keyboard interrupt, doctesting after exiting the debugger not working correctly
|
| Status: |
positive_review →
needs_work
|
| Status: |
needs_work →
needs_review
|
| Status: |
needs_review →
positive_review
|
| Merged in: |
→ sage-5.9.beta4
|
| Resolution: |
→ fixed
|
| Status: |
positive_review →
closed
|
Alright, this works for me on OS X. Needs review.