From 2a274449ae521f0f9cd1a3adc2268a35478a3b6d Mon Sep 17 00:00:00 2001 From: Donald Stufft Date: Wed, 7 Jun 2023 00:26:17 -0400 Subject: [PATCH 1/4] Remove the references to PEP-9999 --- pep-0001.txt | 7 +++++-- pep-0012.rst | 16 +++++++--------- 2 files changed, 12 insertions(+), 11 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 5560a7d744b..032d1672835 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -185,8 +185,11 @@ corrected by the editors). The standard PEP workflow is: * You, the PEP author, fork the `PEP repository`_, and create a file named - ``pep-9999.rst`` that contains your new PEP. Use "9999" as your draft PEP - number. + ``pep-NNNN.rst`` that contains your new PEP. ``NNNN`` should be the next + available PEP number not used by a published or in-PR PEP. + +* In the "PEP:" header field, enter the PEP number that matches your filename + as your draft PEP number. * In the "Type:" header field, enter "Standards Track", "Informational", or "Process" as appropriate, and for the "Status:" diff --git a/pep-0012.rst b/pep-0012.rst index bea8a80836a..bea36dd9ba5 100644 --- a/pep-0012.rst +++ b/pep-0012.rst @@ -60,14 +60,12 @@ Once you've decided which type of PEP yours is going to be, follow the directions below. - Make a copy of this file (the ``.rst`` file, **not** the HTML!) and - perform the following edits. Name the new file ``pep-9999.rst`` if - you don't yet have a PEP number assignment, or ``pep-NNNN.rst`` if - you do. Those with push permissions are welcome to claim the next - available number (ignoring the special blocks 3000 and 8000, and a - handful of special allocations - currently 666, 754, and 801) and - push it directly. - -- Replace the "PEP: 12" header with "PEP: 9999" or "PEP: NNNN", + perform the following edits. Name the new file ``pep-NNNN.rst``, using + the next available number (not used by a published or in-PR PEP, ignoring + the special blocks 3000 and 8000, and a handful of special allocations - + currently 666, 754, and 801). + +- Replace the "PEP: 12" header with "PEP: NNNN", matching the file name. Note that the file name should be padded with zeros (eg ``pep-0012.rst``), but the header should not (``PEP: 12``). @@ -158,7 +156,7 @@ directions below. non-inline link targets referenced by the text. - Run ``./build.py`` to ensure the PEP is rendered without errors, - and check that the output in ``build/pep-9999.html`` looks as you intend. + and check that the output in ``build/pep-NNNN.html`` looks as you intend. - Create a pull request against the `PEPs repository`_. From c914a144e1fbb1c4e088067861334139e2c2888f Mon Sep 17 00:00:00 2001 From: Donald Stufft Date: Wed, 7 Jun 2023 00:43:26 -0400 Subject: [PATCH 2/4] update PEP editor responsibilities --- pep-0001.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 032d1672835..9d996b80a91 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -794,8 +794,9 @@ problem, ask the author(s) to use :pep:`12` as a template and resubmit. Once the PEP is ready for the repository, a PEP editor will: -* Assign a PEP number (almost always just the next available number, - but sometimes it's a special/joke number, like 666 or 3141). +* Check that the author has selected a valid PEP number or assign them a + number if they have not (almost always just the next available number, but + sometimes it's a special/joke number, like 666 or 3141). (Clarification: For Python 3, numbers in the 3000s were used for Py3k-specific proposals. But now that all new features go into Python 3 only, the process is back to using numbers in the 100s again. From 1490d352bc0ccb520f7014b9fe9e23d4101ffcec Mon Sep 17 00:00:00 2001 From: Donald Stufft Date: Wed, 7 Jun 2023 00:45:43 -0400 Subject: [PATCH 3/4] remove references to Py3k --- pep-0001.txt | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 9d996b80a91..2fe4eff8083 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -797,10 +797,8 @@ Once the PEP is ready for the repository, a PEP editor will: * Check that the author has selected a valid PEP number or assign them a number if they have not (almost always just the next available number, but sometimes it's a special/joke number, like 666 or 3141). - (Clarification: For Python 3, numbers in the 3000s were used for - Py3k-specific proposals. But now that all new features go into - Python 3 only, the process is back to using numbers in the 100s again. - Remember that numbers below 100 are meta-PEPs.) + + Remember that numbers below 100 are meta-PEPs. * Check that the author has correctly labeled the PEP's type ("Standards Track", "Informational", or "Process"), and marked its From 7d8d1663fe978f0171eb87c0cb1ae0c86af22d38 Mon Sep 17 00:00:00 2001 From: Donald Stufft Date: Wed, 7 Jun 2023 00:46:26 -0400 Subject: [PATCH 4/4] Apply suggestions from code review Co-authored-by: C.A.M. Gerlach --- pep-0001.txt | 2 +- pep-0012.rst | 8 +++----- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 2fe4eff8083..82ff18ea009 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -185,7 +185,7 @@ corrected by the editors). The standard PEP workflow is: * You, the PEP author, fork the `PEP repository`_, and create a file named - ``pep-NNNN.rst`` that contains your new PEP. ``NNNN`` should be the next + :file:`pep-{NNNN}.rst` that contains your new PEP. :samp:`{NNNN}` should be the next available PEP number not used by a published or in-PR PEP. * In the "PEP:" header field, enter the PEP number that matches your filename diff --git a/pep-0012.rst b/pep-0012.rst index bea36dd9ba5..7ad01dc4342 100644 --- a/pep-0012.rst +++ b/pep-0012.rst @@ -60,10 +60,8 @@ Once you've decided which type of PEP yours is going to be, follow the directions below. - Make a copy of this file (the ``.rst`` file, **not** the HTML!) and - perform the following edits. Name the new file ``pep-NNNN.rst``, using - the next available number (not used by a published or in-PR PEP, ignoring - the special blocks 3000 and 8000, and a handful of special allocations - - currently 666, 754, and 801). + perform the following edits. Name the new file :file:`pep-{NNNN}.rst`, using + the next available number (not used by a published or in-PR PEP). - Replace the "PEP: 12" header with "PEP: NNNN", matching the file name. Note that the file name should be padded with @@ -156,7 +154,7 @@ directions below. non-inline link targets referenced by the text. - Run ``./build.py`` to ensure the PEP is rendered without errors, - and check that the output in ``build/pep-NNNN.html`` looks as you intend. + and check that the output in :file:`build/pep-{NNNN}.html` looks as you intend. - Create a pull request against the `PEPs repository`_.