gh-94087: Update function used to construct Unicode string (in doc and code) #94088
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
I think it meant to refer to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates unicode.rst so that it refers to PyMem_New instead of PyMem_Alloc, a seemingly non-existent function.
This PR also replaces the PyMem_NEW macro with a direct call to PyMem_New, since pymem.h claims PyMEM_NEW is a deprecated alias, and as far as I can tell, there is no reason not to use PyMem_New instead. The other parts of unicode.c use PyMem_New, not PyMem_NEW.
Here's the PyMem_NEW macro, for reference:
#define PyMem_NEW(type, n) PyMem_New(type, n)
I'm not an expert C programmer however so perhaps I'm missing something.