Fix typo: type annotions -> type annotations in PEP 560 comments#504
Merged
Conversation
Member
|
Thanks |
scoder
pushed a commit
that referenced
this pull request
May 18, 2026
Contributor
|
I would avoid putting the misspelling in the commit title because many repos publish changelogs with the title of landed pull requests, which perpetuates the misspelling in the docs. This means that typo discovery tools such as |
Member
|
Oh well… thanks for noting this. :-/ |
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.
The comment
# Allow subscripting <Class> in type annotions (PEP 560)was copy-pasted to four locations with the same typo (annotionsinstead ofannotations). Fixed inbuilder.py,parser.pxi(twice) andsax.py.Comment-only change, no behavioural impact.