MNT: switch how to check for removal of unicode machinery by tacaswell · Pull Request #4789 · cython/cython · GitHub
Skip to content

MNT: switch how to check for removal of unicode machinery - #4789

Closed
tacaswell wants to merge 1 commit into
cython:masterfrom
tacaswell:fix_pyunicode_ready_removal
Closed

tacaswell wants to merge 1 commit into
cython:masterfrom
tacaswell:fix_pyunicode_ready_removal

Conversation

@tacaswell

Copy link
Copy Markdown
Contributor

python/cpython#92537 removed the code from CPython, but left the
public function as a no-op for back compatibility. Thus, even though
the (private) machinery is gone, cython is still trying to use it.

This changes the guard to look at the private function.

closes #4788

python/cpython#92537 removed the code from CPython, but left the
public function as a no-op for back compatibility.  Thus, even though
the (private) machinery is gone, cython is still trying to use it.

This changes the guard to look at the private function.

closes cython#4788
@da-woods

da-woods commented May 13, 2022

Copy link
Copy Markdown
Collaborator

@da-woods

Copy link
Copy Markdown
Collaborator

I think the right way to do this is just a PY_VERSION_HEX check rather than trying to detect is the macros/functions are there.

@scoder

scoder commented May 14, 2022 via email

Copy link
Copy Markdown
Contributor

@tacaswell

Copy link
Copy Markdown
Contributor Author

@tacaswell tacaswell closed this May 15, 2022
@tacaswell
tacaswell deleted the fix_pyunicode_ready_removal branch May 15, 2022 02:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] py312 compatibility

3 participants