Basic requirements (all PEP Types)

• Read and followedPEP 1 &PEP 12
• File created from thelatest PEP template
• PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) andPEP header
• Title clearly, accurately and concisely describes the content in 79 characters or less
• Core dev/PEP editor listed asAuthor orSponsor, and formally confirmed their approval
• Author,Status (Draft),Type andCreated headers filled out correctly
• PEP-Delegate,Topic,Requires andReplaces headers completed if appropriate
• Required sections included
  • Abstract (first section)
  • Copyright (last section; exact wording from template required)
• Code is well-formatted (PEP 7/PEP 8) and is incode blocks, with the right lexer names if non-Python
• PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
• Authors/sponsor added to.github/CODEOWNERS for the PEP

Standards Track requirements

• PEP topicdiscussed in a suitable venue with general agreement that a PEP is appropriate
• Suggested sections included (unless not applicable)
  • Motivation
  • Rationale
  • Specification
  • Backwards Compatibility
  • Security Implications
  • How to Teach This
  • Reference Implementation
  • Rejected Ideas
  • Open Issues
• Python-Version set to valid (pre-beta) future Python version, if relevant
• Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
• Right before or after initial merging,PEP discussion thread created and linked to inDiscussions-To andPost-History

📚 Documentation preview 📚:https://pep-previews--4739.org.readthedocs.build/