Uh oh!
There was an error while loading. Please reload this page.
bpo-36346: Prepare for removing the legacy Unicode C API. - #12409
bpo-36346: Prepare for removing the legacy Unicode C API.#12409serhiy-storchaka wants to merge 32 commits into
Conversation
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.
scoder
left a comment
There was a problem hiding this comment.
Wow, that's a lot of code that will eventually be removed here. Nice!
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
methane
commented
Jun 17, 2020
@serhiy-storchaka Would you split this pull request? |
serhiy-storchaka
commented
Jun 29, 2020
|
Uh oh!
There was an error while loading. Please reload this page.
iritkatriel
commented
Apr 11, 2022
https://bugs.python.org/issue36346 is closed. What is the status of this PR? |
serhiy-storchaka
commented
May 12, 2022
No longer actual after merging #92537. |
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.
https://bugs.python.org/issue36346