From 0d346217d77e66521a5c43d6022dcc3de3f3f68c Mon Sep 17 00:00:00 2001 From: Srushti Pampat Date: Wed, 21 Oct 2026 22:17:31 +0530 Subject: [PATCH] Clarify PEP number assignment workflow --- peps/pep-0001.rst | 24 ++++-------------------- 1 file changed, 4 insertions(+), 20 deletions(-) diff --git a/peps/pep-0001.rst b/peps/pep-0001.rst index e90d7ff8787..07ea51aec92 100644 --- a/peps/pep-0001.rst +++ b/peps/pep-0001.rst @@ -107,8 +107,8 @@ PEP Editors ----------- The PEP editors are individuals responsible for managing the administrative -and editorial aspects of the PEP workflow (e.g. assigning PEP numbers and -changing their status). See `PEP Editor Responsibilities & Workflow`_ for +and editorial aspects of the PEP workflow (e.g. overseeing PEP number allocation +and changing PEP status). See `PEP Editor Responsibilities & Workflow`_ for details. PEP editorship is by invitation of the current editors, and they can be @@ -225,8 +225,6 @@ The standard PEP workflow is: If the PEP isn't ready for approval, an editor will send it back to the author for revision, with specific instructions. -* Once approved, they will assign your PEP a number. - Once the review process is complete, and the PEP editors approve it (note that this is *not* the same as accepting your PEP!), they will squash commit your pull request onto main. @@ -237,21 +235,8 @@ not providing proper motivation or addressing backwards compatibility, or not in keeping with the Python philosophy. The Steering Council can be consulted during the approval phase, and are the final arbiter of a draft's PEP-ability. -Developers with write access to the `PEP repository`_ may claim PEP -numbers directly by creating and committing a new PEP. When doing so, the -developer must handle the tasks that would normally be taken care of by the -PEP editors (see `PEP Editor Responsibilities & Workflow`_). This includes -ensuring the initial version meets the expected standards for submitting a -PEP. Alternately, even developers should submit PEPs via pull request. -When doing so, you are generally expected to handle the process yourself; -if you need assistance from PEP editors, mention ``@python/pep-editors`` -on GitHub. - As updates are necessary, the PEP author can check in new versions if they (or a collaborating developer) have write access to the `PEP repository`_. -Getting a PEP number assigned early can be useful for ease of -reference, especially when multiple draft PEPs are being considered at the -same time. Standards Track PEPs consist of two parts, a design document and a reference implementation. It is generally recommended that at least a @@ -263,8 +248,7 @@ test of implementation. Discussing a PEP ---------------- -As soon as a PEP number has been assigned -and the draft PEP is committed to the `PEP repository`_, +Once the draft PEP is committed to the `PEP repository`_, a discussion thread for the PEP should be created to provide a central place to discuss and review its contents, and the PEP should be updated so that the ``Discussions-To`` header links to it. @@ -310,7 +294,7 @@ subject matter, and picking an appropriately-specialized discussion for the PEP's topic (if applicable) should be considered. PEP authors should use their discretion here. -Once the PEP is assigned a number and committed to the PEP repository, +Once the PEP is committed to the PEP repository, substantive issues should generally be discussed on the canonical public thread, as opposed to private channels, GitHub pull request reviews or unrelated venues. This ensures everyone can follow and contribute,