Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 4bb1dc4e2cec by Vinay Sajip in branch '2.7':
Closes #13232: Handle multiple encodings in exception logging.
http://hg.python.org/cpython/rev/4bb1dc4e2cec
--
nosy: +python-dev
resolution: - fixed
stage: test
Changes by Thomas Guettler guet...@thomas-guettler.de:
Added file: http://bugs.python.org/file23486/unicodedecodeerror-in-logging.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13232
___
Thomas Guettler guet...@thomas-guettler.de added the comment:
I attached a testcase (unicodedecodeerror-in-logging.py). If the
filesystemencoding is UTF-8 and the source code is encoded in latin1, then the
logging fails. It happens because there is a German umlaut in the comment
behind 1/0.
New submission from Thomas Guettler guet...@thomas-guettler.de:
In changeset fe6be0426e0d the format() method was changed. Unfortunately it
does not catch all unicode decode errors.
I think line 482 of logging/__init__.py should be modified:
to this (add 'replace'):
s = s +
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Can you tell me what the actual data was which failed to be decoded? Is there
more than one encoding in effect (e.g. one for the filesystem, and another for
the other data in the exception being logged)?
--
nosy: +vinay.sajip
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - test needed
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13232
___
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13232
___
___
