Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

StanFromIreland
Copy link
Member

@StanFromIreland StanFromIreland commented Sep 10, 2025

Basic requirements (all PEP Types)

  • Read and followed PEP 1 & PEP 12
  • File created from the latest PEP template
  • PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
  • Title clearly, accurately and concisely describes the content in 79 characters or less
  • Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
  • Author, Status (Draft), Type and Created headers filled out correctly
  • PEP-Delegate, Topic, Requires and Replaces 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 in code 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 topic discussed 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 in Discussions-To and Post-History

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

@StanFromIreland StanFromIreland requested a review from a team as a code owner September 10, 2025 15:37
@StanFromIreland StanFromIreland added the new-pep A new draft PEP submitted for initial review label Sep 10, 2025
@StanFromIreland StanFromIreland marked this pull request as draft September 10, 2025 15:37
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps more of a comment for Discourse, but are you aware that we already back up the repo (including all the GH metadata not in the Git repo)?

I'm not sure what this PEP gives on top of that. Perhaps worth having a pre-PEP discussion before going directly to the PEP stage?

cc @ezio-melotti @StanFromIreland

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AA-Turner AA-Turner changed the title PEP 807: Creation of a CPython mirror PEP 9999: Creation of a CPython mirror Sep 10, 2025
@AA-Turner
Copy link
Member

There's now a pre-PEP discussion thread so I'll unassign the number for now.

A

@StanFromIreland
Copy link
Member Author

Moving to core-development instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-pep A new draft PEP submitted for initial review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants