Gregory P. Smith <g...@krypto.org> added the comment: http://pypi.python.org/pypi/unittest2 says
"There are several places in unittest2 (and unittest) that call str(...) on exceptions to get the exception message. This can fail if the exception was created with non-ascii unicode. This is rare and I won't address it unless it is actually reported as a problem for someone." It is a problem for us now that we've re-rooted all our TestCases on top of unittest2 at work. :) The solution I'm leaning towards is monkey-patching the new traceback._some_str implementation in at unittest2 import time. ---------- nosy: +gregory.p.smith _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8313> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
