This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients amaury.forgeotdarc, ezio.melotti, gregory.p.smith, gthb, michael.foord, vstinner
Date 2011-12-23.02:32:03
SpamBayes Score 0.00010415989
Marked as misclassified No
Message-id <1324607524.87.0.53475097696.issue8313@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2011-12-23 02:32:05gregory.p.smithsetrecipients: + gregory.p.smith, amaury.forgeotdarc, vstinner, ezio.melotti, michael.foord, gthb
2011-12-23 02:32:04gregory.p.smithsetmessageid: <1324607524.87.0.53475097696.issue8313@psf.upfronthosting.co.za>
2011-12-23 02:32:04gregory.p.smithlinkissue8313 messages
2011-12-23 02:32:03gregory.p.smithcreate