Repository navigation
Comment typo fixes only (no code changes) in Python/ (no LLM used) - #159097
Closed
willy-b wants to merge 2 commits into
Closed
willy-b wants to merge 2 commits into
willy-b wants to merge 2 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Author
|
(This will show failing checks until a team-member adds the "skip news" and "skip issue" labels, which I think should be appropriate for a typo only PR per cpython/.github/PULL_REQUEST_TEMPLATE.md Line 15 in 0ec3aee |
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
Nons of those typos are user facing so we do not accept them in general, sorry. |
Sorry, something went wrong.
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
Reviewers
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.
Just finding and fixing some typos in the code comments (no effect on behavior, no actual code changes in this PR) while taking time to study the codebase. Note there are a couple of other such typos not included here that are already in the pending-review PR #157879 .
Thanks so much to the Python team for the excellent language, community, and tool ecosystem, hopefully these typos are useful to fix.