-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix typos in PEPs using codespell #3909
Conversation
IMO these are all small changes - a bunch of simple and non-controversial spelling corrections, plus associated infrastructure - so I'm fine with it all being one PR. There's one false positive, but otherwise LGTM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, these LGTM!
Note: In addition to the changes requested/suggested by @AA-Turner and @hugovk in review, I've added the extra ignore directories:
|
It seems codespell was last run on peps up to around 481 since there's only one typo up to pep 100 and many thereafter.
… mode (without names)
aa6e867
to
67bca51
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
It seems codespell was last run on peps up to around 481, since there's only one typo up to pep 100 and many thereafter.
Is this ok or do I need to make a separate PR for each PEP? That would be 18 which would be a bit annoying but I can do it if there should be no exception to the rule.
I ran codespell from main (commit codespell-project/codespell@f8e1b5f) with the following invokation:
📚 Documentation preview 📚: https://pep-previews--3909.org.readthedocs.build/