docs: remove unnecessary PEP references in libraries guide#2288
Merged
JelleZijlstra merged 1 commit intoMay 16, 2026
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
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.
Summary
This PR removes a few unnecessary PEP references from the Typing Python Libraries guide and replaces them with more user-focused wording and documentation references.
Changes made
PEP 484overload reference withtyping.overloaddocumentation wording.PEP 484.PEP 613wording in the type alias example with directTypeAliasterminology.These changes align with the goal of preferring documentation-oriented references over direct PEP references where appropriate, while keeping important specification-related PEP references intact.
Related to #2150