Hi Julien On 2012-05-03, Julien Puydt <julien.pu...@laposte.net> wrote: >> However, when I give the same commands in an interactive session >> (without change_warning_output(sys.stdout), since I don't know where >> to import that from), there is no crash. That's not good for >> debugging. I could try to control garbage collection, though. Perhaps >> that's triggering the crash. > > I suggest to modify the .py by commenting out that line, then run > the non-interactive test -- to see if it's indeed the culprit.
change_warning_output(sys.stdout) is not part of the doc test, but it is added by the doctest framework. Hence, I can't comment it out. In order to test whether it is really the culprit, I'd rather like to know where I can that command import from, so that I can add when executing the test on the command line. Best regards, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
