bpo-39500: Document PyUnicode_IsIdentifier() function#18397
Merged
Conversation
Member
Author
|
@serhiy-storchaka: here is a different approach. Instead of returning -1 on error and require all callers to be modified to start checking for error, I modified the function to never fail. If the string is not ready, I use the legacy API to access it ( Previous attempt: PR #18280. |
PyUnicode_IsIdentifier() does not call Py_FatalError() anymore if the string is not ready.
Member
Author
|
I modified my PR to use _PyUnicode_WSTR() and |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
PyUnicode_IsIdentifier() does not call Py_FatalError() anymore if the
string is not ready.
https://bugs.python.org/issue39500