gh-137267: Clarify bytes.isalnum and bytearray.isalnum doc wording #137269
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
bedevere-app
bot
added
awaiting review
docs
|
Hi @AA-Turner , i just checked the issue section, it's not resolved, can i open my PR once again for the review , Thanks |
|
See #137267 (comment). A |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 fixes a minor wording issue in the documentation of
bytes.isalnum()andbytearray.isalnum()inDoc/library/stdtypes.rst.Changes:
These methods return True when all bytes are alphabetic ASCII characters and/or digits, so the updated wording improves clarity and correctness.
bytes.isalnum()andbytearray.isalnum()should sayalphabetic ASCII characters and/or ASCII decimal digits#137267📚 Documentation preview 📚: https://cpython-previews--137269.org.readthedocs.build/