[issue13830] codecs error handler is called with a UnicodeDecodeError with the same args

Serhiy Storchaka added the comment: For reference, this behavior was from beginning, since implementing PEP 293 in issue432401. -- ___ Python tracker ___ _

[issue13830] codecs error handler is called with a UnicodeDecodeError with the same args

Change by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue13830] codecs error handler is called with a UnicodeDecodeError with the same args

STINNER Victor added the comment: Codec encoders reuse the same exception object for speed, but set some attributes (start, end and reason). Recreate the args tuple each time that a attribute is set. UnicodeEncodeError and UnicodeDecodeError should maybe override args getter to create a new t

[issue13830] codecs error handler is called with a UnicodeDecodeError with the same args

Walter Dörwald added the comment: See this ancient posting about this problem: http://mail.python.org/pipermail/python-dev/2002-August/027661.html (see point 4.). So I guess somebody did finally complain! ;) The error attributes are documented in PEP 293. The existence of the attributes i

[issue13830] codecs error handler is called with a UnicodeDecodeError with the same args

Changes by Éric Araujo : -- nosy: +haypo, lemburg ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue13830] codecs error handler is called with a UnicodeDecodeError with the same args

New submission from Amaury Forgeot d'Arc : The script below shows that the error handler is always called with the same error object. The 'start', 'end', and 'reason' properties are correctly updated, but the 'args' is always the same and holds the values used for the first call. It's a bit