R. David Murray added the comment: It looks like a bug in the tracing machinery that has only been revealed by the changes to how tracebacks are interpreted in python3. It should be a relatively simple fix, but I wonder if there is existing code that depends on the second argument getting turned into a string.
You can hack around the problem by creating a class to wrap around the arg[1] you get that has __cause__ and __context__ attributes, both set to none, and whose __str__ returns the original string. ---------- keywords: +easy nosy: +r.david.murray stage: -> needs patch title: format_exception() breask on exception tuples from trace function -> format_exception() breaks on exception tuples from trace function versions: +Python 3.2, Python 3.4 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17413> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
