Message150127
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. |
|
Date |
User |
Action |
Args |
2011-12-23 02:32:05 | gregory.p.smith | set | recipients:
+ gregory.p.smith, amaury.forgeotdarc, vstinner, ezio.melotti, michael.foord, gthb |
2011-12-23 02:32:04 | gregory.p.smith | set | messageid: <1324607524.87.0.53475097696.issue8313@psf.upfronthosting.co.za> |
2011-12-23 02:32:04 | gregory.p.smith | link | issue8313 messages |
2011-12-23 02:32:03 | gregory.p.smith | create | |
|