Skip to content

Conversation

@serhiy-storchaka
Copy link
Member

@serhiy-storchakaserhiy-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-storchakaserhiy-storchaka merged commit 4c8f09d into python:masterJul 10, 2020
@serhiy-storchakaserhiy-storchaka deleted the do-not-use-wchar-cache branch July 10, 2020 20:26
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 freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@serhiy-storchaka@the-knights-who-say-ni@bedevere-bot