I've also been getting the "mysterious error may have crashed doctest" messages, and on closer inspection I think there's actually a bug *in the doctest framework*, which causes it to report all failed doctests as "mysterious errors". I tested this myself by creating a Python file with a single function whose doctest read
r" EXAMPLE: sage: 2 1 " and sure enough running sage -t on this gave a "mysterious" error. Running sage -t -verbose reports correctly what the failed doctest actually was. Like John I've been doing this on a build upgraded from 3.2.1. I got two failed doctests doing sage -testall -- one in sage/rings/ number_field/number_field_morphism.py (a numerical noise issue that I pointed out on the #4276 trac thread) and one in sage/misc/ cachefunc.py. David --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
