Message184125
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. |
|
Date |
User |
Action |
Args |
2013-03-14 01:26:48 | r.david.murray | set | recipients:
+ r.david.murray, inducer |
2013-03-14 01:26:48 | r.david.murray | set | messageid: <1363224408.38.0.826084191476.issue17413@psf.upfronthosting.co.za> |
2013-03-14 01:26:48 | r.david.murray | link | issue17413 messages |
2013-03-14 01:26:47 | r.david.murray | create | |
|