Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-36346: Make using the legacy Unicode C API optional #21437

Merged

Conversation

serhiy-storchaka
Copy link
Member

@serhiy-storchaka serhiy-storchaka commented Jul 10, 2020

Do not use the legacy Unicode C API which depends on the wchar_t* cache if USE_UNICODE_WCHAR_CACHE is defined as false.

It can help to test in advance the effect of removing the wchar_t* cache.

https://bugs.python.org/issue36346

Add two compile time options: HAVE_UNICODE_WCHAR_CACHE and
USE_UNICODE_WCHAR_CACHE.

USE_UNICODE_WCHAR_CACHE makes the interpreter not using the
wchar_t cache and the legacy Unicode C API.

HAVE_UNICODE_WCHAR_CACHE removes the wchar_t cache and the
legacy Unicode C API that depends on it.
@serhiy-storchaka serhiy-storchaka merged commit 4c8f09d into python:master Jul 10, 2020
@serhiy-storchaka serhiy-storchaka deleted the do-not-use-wchar-cache branch July 10, 2020 20:26
arun-mani-j pushed a commit to arun-mani-j/cpython that referenced this pull request Jul 21, 2020
Add compile time option USE_UNICODE_WCHAR_CACHE. Setting it to 0
makes the interpreter not using the wchar_t cache and the legacy Unicode C API.
shihai1991 pushed a commit to shihai1991/cpython that referenced this pull request Aug 20, 2020
Add compile time option USE_UNICODE_WCHAR_CACHE. Setting it to 0
makes the interpreter not using the wchar_t cache and the legacy Unicode C API.
xzy3 pushed a commit to xzy3/cpython that referenced this pull request Oct 18, 2020
Add compile time option USE_UNICODE_WCHAR_CACHE. Setting it to 0
makes the interpreter not using the wchar_t cache and the legacy Unicode C API.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants