Nick Coghlan added the comment: For testing, you can create a recursive scenario that terminates with an exception after a defined number of iterations:
>>> def f(counter): ... if counter: ... f(counter-1) ... else: ... raise RuntimeError ... >>> f(3) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "<stdin>", line 3, in f File "<stdin>", line 3, in f File "<stdin>", line 3, in f File "<stdin>", line 5, in f RuntimeError It's probably also worth checking the handling of two distinct frame repetitions by having another recursion counter that terminates itself by calling the one that terminates by raising an exception Beyond that, https://hg.python.org/cpython/file/tip/Lib/test/test_traceback.py covers both traceback formatting implementations, so a new test case in TracebackFormatTests seems appropriate. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26823> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
