Repository navigation
Fix typos flagged by codespell - #5222
Merged
Merged
Conversation
Corrects twelve misspellings that the repository's own codespell configuration reports. The spelling check runs with continue-on-error in the lint workflow, so these never failed CI and accumulated unnoticed. targetting -> targeting (PEP 739 x2, PEP 793) possibily -> possibility (PEP 739) mistakingly -> mistakenly (PEP 755) reponsibilities -> responsibilities (PEP 773) introducted -> introduced (PEP 777) unforseen -> unforeseen (PEP 783) succesfully -> successfully (PEP 793 examplemodule.c) wrapepd -> wrapped (PEP 797) taged -> tagged (PEP 820) intepreter -> interpreter (release_management) One of the PEP 739 fixes is in python-build-info-v1.0.schema.json, whose description field repeats the sentence corrected in the PEP body; the file still parses as valid JSON. Prose only; no PEP headers, metadata or normative wording changed. Words codespell still reports are left alone deliberately: "Bloc" is the Bloc STAR voting method, "Stange" is Markus Stange, "indx" and "ExceptionN" appear in code samples, "pre-emptively", "transferrable" and "useable" are accepted variants, and "respondants" sits in PEP 308 and PEP 378, which are historical records from 2003.
Dhairya-007
requested review from
a team,
ZeroIntensity,
ambv,
emmatyping,
encukou,
hoodmane,
warsaw and
zooba
as code owners
November 6, 2026 17:16
|
All commit authors signed the Contributor License Agreement. |
Documentation build overview
8 files changed ·
|
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
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.
Corrects twelve misspellings that the repository's own codespell configuration already reports.
The spelling check runs with
continue-on-error: trueinlint.yml, so these never failed CI and accumulated unnoticed.codespellgoes from 70 reported words to 58 with this change.targettingtargetingpossibilypossibilitymistakinglymistakenlyreponsibilitiesresponsibilitiesintroductedintroducedunforseenunforeseensuccesfullysuccessfullyexamplemodule.cwrapepdwrappedtagedtaggedintepreterinterpreterrelease_management/python-releases.tomlOne of the PEP 739 fixes is in
python-build-info-v1.0.schema.json, whosedescriptionrepeats verbatim the sentence corrected in the PEP body, so the two stay consistent. I checked the file still parses as valid JSON.Prose only — no PEP headers, metadata or normative wording is changed.
Deliberately left alone
The words codespell still reports are not typos:
Bloc(PEP 13) — the Bloc STAR voting methodStange(PEP 831) — Markus Stange, a person's nameindx,ExceptionN(PEP 323, PEP 463) — identifiers and placeholder notation in code samplespre-emptively,transferrable,useable— accepted variant spellingsrespondants(PEP 308, PEP 378) — a genuine misspelling, but those PEPs are historical records from 2003, so I left them untouched rather than edit the record. Happy to include them if preferred..drawio.svgfiles underpeps/pep-0694/