Message147194
Thanks, Florent. This patch was by you in response to issue #8201 - do you have any suggestion as to the best way to resolve this? I tried changing the non-ASCII logger to '\xc3\xb4\xc3\xbc', which decodes cleanly to u'\xf4\xfc' (o-circumflex u-umlaut), but it apparently still fails to convert to Unicode when doing the comparison, and so still raises the warning. Is there any byte-string sequence which won't give the error in this circumstance? Obviously I could convert it to Unicode, but then the test is checking correct operation when you have a non-ASCII (byte-)string name as well as a Unicode name for loggers. |
|
Date |
User |
Action |
Args |
2011-11-06 23:12:22 | vinay.sajip | set | recipients:
+ vinay.sajip, ezio.melotti, flox |
2011-11-06 23:12:22 | vinay.sajip | set | messageid: <1320621142.9.0.571674757754.issue13356@psf.upfronthosting.co.za> |
2011-11-06 23:12:22 | vinay.sajip | link | issue13356 messages |
2011-11-06 23:12:22 | vinay.sajip | create | |
|