[issue31393] Fix the use of PyUnicode_READY()

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue31393] Fix the use of PyUnicode_READY()

Serhiy Storchaka added the comment: New changeset ddb536ba7b7c6022424e39d666c3cc81772645c0 by Serhiy Storchaka in branch '3.6': [3.6] bpo-31393: Fix the use of PyUnicode_READY(). (GH-3451). (#3453) https://github.com/python/cpython/commit/ddb536ba7b7c6022424e39d666c3cc81772645c0 -- _

[issue31393] Fix the use of PyUnicode_READY()

Changes by Serhiy Storchaka : -- pull_requests: +3450 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue31393] Fix the use of PyUnicode_READY()

Serhiy Storchaka added the comment: New changeset e3b2b4b8d9e751b49e3550cb83ba39b54fdc377c by Serhiy Storchaka in branch 'master': bpo-31393: Fix the use of PyUnicode_READY(). (#3451) https://github.com/python/cpython/commit/e3b2b4b8d9e751b49e3550cb83ba39b54fdc377c -- ___

[issue31393] Fix the use of PyUnicode_READY()

Changes by Serhiy Storchaka : -- keywords: +patch pull_requests: +3449 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue31393] Fix the use of PyUnicode_READY()

New submission from Serhiy Storchaka: PyUnicode_READY() raises an exception when returns -1 (MemoryError or ValueError). Not all code that calls PyUnicode_READY() handles this property. The following PR fixes all uses of PyUnicode_READY(). * If PyUnicode_READY() returns -1 the caller should ei