Nick Coghlan added the comment: Indeed, the traceback abbreviation doesn't try to detect recursive loops, only exactly duplicated lines.
The problem is that the more state management we do in the traceback printing, the higher the chance there is of getting an error while attempt to display the previous errors. Keeping the immediately preceding entry and doing an exact comparison is straightforward, but pattern matching on up-to-N entries is something we'll leave to external traceback pretty printers. ---------- resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29855> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
