• Change is either:
  • To a Draft PEP
  • To an Accepted or Final PEP, with Steering Council approval
  • To fix an editorial issue (markup, typo, link, header, etc)
• PR title prefixed with PEP number (e.g.PEP 123: Summary of changes)

This PR contains substantial updates to PEP 750 based on feedback from the broader Python community, including comments on theofficial PEP Discourse thread and in-person core team feedback at the recent Bellevue, WA, USA sprint.

It has been reviewed by:

• @lysnikolaou (in progress)
• @pauleveritt
• @jimbaker
• @koxudaxi
• @davepeck

Koudai Aono (@koxudaxi) and I were both added as co-authors.

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 (not relevant?)
• Right before or after initial merging,PEP discussion thread created and linked to inDiscussions-To andPost-History (the existing Discourse thread isfound here )

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