Repository navigation
PEP 837: Name Resolution in Class Namespaces - #5042
Merged
Merged
Conversation
First draft of PEP: Name Resolution in Class Namespaces
For PEP 837
|
All commit authors signed the Contributor License Agreement. |
Fix references to other PEPs.
Documentation build overview
5 files changed ·
|
Once again try to fix PEP references
Trailing whitespace
ethanfurman
pushed a commit
to ethanfurman/peps
that referenced
this pull request
Oct 8, 2026
## Basic requirements (all PEP Types) * [x] Read and followed [PEP 1](https://peps.python.org/1) & [PEP 12](https://peps.python.org/12) * [x] File created from the [latest PEP template](https://github.com/python/peps/blob/main/peps/pep-0012/pep-NNNN.rst?plain=1) * [x] PEP has next available number, & set in filename (``pep-NNNN.rst``), PR title (``PEP 123: <Title of PEP>``) and ``PEP`` header * [x] Title clearly, accurately and concisely describes the content in 79 characters or less * [x] Core dev/PEP editor listed as ``Author`` or ``Sponsor``, and formally confirmed their approval * [x] ``Author``, ``Status`` (``Draft``), ``Type`` and ``Created`` headers filled out correctly * [x] ``PEP-Delegate``, ``Topic``, ``Requires`` and ``Replaces`` headers completed if appropriate (none applicable) * [x] Required sections included * [x] Abstract (first section) * [x] Copyright (last section; exact wording from template required) * [x] Code is well-formatted (PEP 7/PEP 8) and is in [code blocks, with the right lexer names](https://peps.python.org/pep-0012/#literal-blocks) if non-Python * [x] PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML * [x] Authors/sponsor added to ``.github/CODEOWNERS`` for the PEP ## Standards Track requirements * [x] PEP topic [discussed in a suitable venue](https://peps.python.org/pep-0001/#start-with-an-idea-for-python) with general agreement that a PEP is appropriate * [x] [Suggested sections](https://peps.python.org/pep-0012/#suggested-sections) included (unless not applicable) * [x] Motivation * [ ] Specification * [ ] Rationale * [ ] Backwards Compatibility * [ ] Security Implications * [ ] How to Teach This * [ ] Reference Implementation * [ ] Rejected Ideas * [ ] Open Issues
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.
Basic requirements (all PEP Types)
pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) andPEPheaderAuthororSponsor, and formally confirmed their approvalAuthor,Status(Draft),TypeandCreatedheaders filled out correctlyPEP-Delegate,Topic,RequiresandReplacesheaders completed if appropriate (none applicable).github/CODEOWNERSfor the PEPStandards Track requirements