[issue35365] Use wchar_t* buffer instead of Unicode object in code page decoder

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue35365] Use wchar_t* buffer instead of Unicode object in code page decoder

Serhiy Storchaka added the comment: New changeset eeb719eac6347f5b6e85389aa13a386024766806 by Serhiy Storchaka in branch 'master': bpo-35365: Use a wchar_t* buffer in the code page decoder. (GH-10837) https://github.com/python/cpython/commit/eeb719eac6347f5b6e85389aa13a386024766806

[issue35365] Use wchar_t* buffer instead of Unicode object in code page decoder

Change by Serhiy Storchaka : -- dependencies: +Code page decoder incorrectly handles input >2GiB ___ Python tracker ___ ___ Python-b

[issue35365] Use wchar_t* buffer instead of Unicode object in code page decoder

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +10075 stage: -> patch review ___ Python tracker ___ ___ Python-bug

[issue35365] Use wchar_t* buffer instead of Unicode object in code page decoder

New submission from Serhiy Storchaka : Currently the code page decoder uses the legacy Unicode C API for creating an output buffer as a Unicode object with PyUnicode_WCHAR_KIND. Proposed PR makes it using a raw wchar_t* buffer. This is necessary for deprecating and removing the legacy Unicode