[issue18509] CJK decoders should return MBERR_EXCEPTION on PyUnicodeWriter error

STINNER Victor added the comment: I should now be fixed. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue18509] CJK decoders should return MBERR_EXCEPTION on PyUnicodeWriter error

Roundup Robot added the comment: New changeset f63d34cd3714 by Victor Stinner in branch 'default': Issue #18509: handle PyUnicode_Writer() error http://hg.python.org/cpython/rev/f63d34cd3714 -- nosy: +python-dev ___ Python tracker

[issue18509] CJK decoders should return MBERR_EXCEPTION on PyUnicodeWriter error

Larry Hastings added the comment: It's a month before beta 1. This weekend is alpha 4; it'd be nice if it were fixed for that, of course, but that does not seem likely. -- ___ Python tracker _

[issue18509] CJK decoders should return MBERR_EXCEPTION on PyUnicodeWriter error

STINNER Victor added the comment: > Victor, are you going to write a patch for this before beta 1? Not before at least one week, I'm busy on tracemalloc. If anyone is interesting, please write a patch and I will review it :-) (The CJK macros are ugly!) -- _

[issue18509] CJK decoders should return MBERR_EXCEPTION on PyUnicodeWriter error

Larry Hastings added the comment: Victor, are you going to write a patch for this before beta 1? -- ___ Python tracker ___ ___ Python-

[issue18509] CJK decoders should return MBERR_EXCEPTION on PyUnicodeWriter error

STINNER Victor added the comment: This is a regression of Python 3.4, so it would be nice to fix it before the Python 3.4 final. -- nosy: +larry priority: normal -> release blocker ___ Python tracker _

[issue18509] CJK decoders should return MBERR_EXCEPTION on PyUnicodeWriter error

New submission from STINNER Victor: I modified CJK codecs to reuse the new PyUnicodeWriter API (to use the PEP 393 instead of Py_UNICODE*). The problem is that PyUnicodeWriter error is not handled correctly: the decoder should return MBERR_EXCEPTION, whereas the error is not handled at all cur