From b0e74392db6f253d631e629344f4f48ca9b2422f Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Mon, 9 Jan 2023 13:37:36 -0600
Subject: [PATCH 01/13] Add baseline Other template following existing

---
 .github/PULL_REQUEST_TEMPLATE/other.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 .github/PULL_REQUEST_TEMPLATE/other.md

diff --git a/.github/PULL_REQUEST_TEMPLATE/other.md b/.github/PULL_REQUEST_TEMPLATE/other.md
new file mode 100644
index 00000000000..b8a116e9f53
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/other.md
@@ -0,0 +1,18 @@
+---
+name: Other
+about: Any PR that doesn't fall in the other categories
+---
+
+<!--
+
+*Please* read our Contributing Guidelines (CONTRIBUTING.rst)
+before submitting an issue or pull request to this repository,
+to make sure this repo is the appropriate venue for your proposed change.
+
+Prefix the pull request title with the PEP number; for example:
+
+PEP NNN: Summary of the changes made
+
+Thanks!
+
+-->

From 1c2a44ae278d8b98976523066ac07a93f984151e Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Mon, 9 Jan 2023 13:38:07 -0600
Subject: [PATCH 02/13] Add New PEP template and checklist

---
 .github/PULL_REQUEST_TEMPLATE/new-pep.md | 72 ++++++++++++++++++++++++
 1 file changed, 72 insertions(+)
 create mode 100644 .github/PULL_REQUEST_TEMPLATE/new-pep.md

diff --git a/.github/PULL_REQUEST_TEMPLATE/new-pep.md b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
new file mode 100644
index 00000000000..16fee30ee41
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
@@ -0,0 +1,72 @@
+---
+name: New PEP
+about: Submit a new draft PEP for consideration
+labels: "new-pep"
+---
+
+<!--
+
+Please read and follow PEP 1 and PEP 12 before submitting a new PEP:
+
+https://peps.python.org/pep-0001/#submitting-a-pep
+
+https://peps.python.org/pep-0012/#how-to-use-this-template
+
+Make sure to include the PEP number in the pull request title; for example:
+
+PEP 9999: <Title of PEP>
+
+See our Contributing Guidelines (CONTRIBUTING.rst) for more information.
+
+Thanks!
+
+-->
+
+
+# New PEP
+
+<!--
+
+Briefly describe your new PEP here, and anything else we should know.
+Be sure to link to any previous discussions or issues motivating/drafting it.
+
+-->
+
+
+
+## Checklist
+
+<!--
+
+You should use the following as a guide when double-checking your PEP,
+and you can help complete some of it yourself if you like
+by ticking any boxes you're sure about, like this: [x]
+
+If you're unsure about anything, just leave it blank and we'll take a look.
+
+-->
+
+* [ ] File created from the [latest PEP template](https://github.com/python/peps/blob/main/pep-0012/pep-NNNN.rst?plain=1)
+
+### Content requirements
+
+* [ ] PEP topic [discussed in a suitable venue](https://peps.python.org/pep-0001/#start-with-an-idea-for-python) and general agreement that a PEP is appropriate
+* [ ] Content is reasonably sound, complete and makes at least basic technical sense
+* [ ] Abstract and Copyright sections completed, with the required wording in the latter
+* [ ] [Suggested sections](https://peps.python.org/pep-0012/#suggested-sections) included (unless not applicable)
+* [ ] Title clearly, accurately and concisely describes the content
+* [ ] Prose is intelligible and generally free of basic grammar and syntax errors, at least to the degree they significantly detract from understanding
+* [ ] Code is in code blocks, well-formatted (PEP 7/PEP 8) and has the right [lexer name](https://pygments.org/docs/lexers/) if non-Python (or ``text``)
+* [ ] Any project stated in the PEP as supporting/endorsing benefiting from it confirms such
+
+
+### Technical requirements
+
+* [ ] Filename in the correct format (``pep-NNNN.rst``)
+* [ ] ``PEP``, ``Title``, ``Author``, ``Status`` (``Draft``), ``Type`` and ``Created`` headers filled out correctly
+* [ ] ``PEP-Delegate``, ``Requires``, ``Python-Version`` and ``Replaces`` filled out if appropriate
+* [ ] ``Sponsor`` listed and approves if not authored by a core dev or PEP editor
+* [ ] PEP builds with no warnings, CI checks pass and content displays as intended in the rendered preview
+* [ ] PEP number assigned by the PEP editors and filename & ``PEP`` header updated accordingly
+* [ ] Sponsor/author(s) that are core devs/PEP editors added to ``.github/CODEOWNERS`` for the PEP
+* [ ] Right before or after initial merging, [PEP discussion thread](https://peps.python.org/pep-0001/#discussing-a-pep) created and linked to in ``Discussions-To`` and ``Post-History``

From 1a1cee7ca117860f99a2d9ffe9160809fd7df220 Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Mon, 9 Jan 2023 13:38:30 -0600
Subject: [PATCH 03/13] Add Accept/Reject PEP template and checklist

---
 .../accept-reject-pep.md                      | 50 +++++++++++++++++++
 1 file changed, 50 insertions(+)
 create mode 100644 .github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md

diff --git a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
new file mode 100644
index 00000000000..b3f55308e1e
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
@@ -0,0 +1,50 @@
+---
+name: Accept/Reject PEP
+about: Mark a draft PEP as accepted or rejected
+---
+
+<!--
+
+See PEP 1 for more details about the PEP review and resolution process:
+
+https://peps.python.org/pep-0001/#pep-review-resolution
+
+Make sure to include the PEP number in the pull request title; for example:
+
+PEP NNN: Mark as Accepted/Rejected
+
+Thanks!
+
+-->
+
+
+# Accept/Reject PEP
+
+<!--
+
+Link to the official acceptance/rejection message
+by the Steering Council/PEP Delegate on the PEP's discussion thread.
+
+-->
+
+
+
+## Checklist
+
+<!--
+
+This lists the key steps needed to mark a PEP as Accepted/Rejected.
+
+You can help complete it yourself if you like
+by ticking any boxes you're sure about, like this: [x]
+
+If you're unsure about anything, just leave it blank and we'll take a look.
+
+-->
+
+
+* [ ] SC/PEP Delegate has formally accepted/rejected the PEP and posted to the ``Discussions-To`` thread
+* [ ] ``Status`` changed to ``Accepted``/``Rejected``
+* [ ] ``Resolution`` link points directly to SC/PEP Delegate official acceptance/rejected post
+* [ ] Acceptance/rejection notice added, if the SC/PEP delegate had any major conditions or critical commentary (and any changes made accordingly)
+* [ ] ``Discussions-To``, ``Post-History` and ``Python-Version`` complete and up to date

From 499a9fab031bef1fdd815e6f71830b8b444631fb Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Mon, 9 Jan 2023 13:38:55 -0600
Subject: [PATCH 04/13] Add Mark PEP Final template and checklist

---
 .../PULL_REQUEST_TEMPLATE/mark-pep-final.md   | 48 +++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 .github/PULL_REQUEST_TEMPLATE/mark-pep-final.md

diff --git a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
new file mode 100644
index 00000000000..cb049aa2f1f
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
@@ -0,0 +1,48 @@
+---
+name: Mark PEP Final
+about: Mark an Accepted PEP as Final
+---
+
+<!--
+
+See PEP 1 for more about the PEP lifecycle and when one is considered Final:
+
+https://peps.python.org/pep-0001/#pep-review-resolution
+
+Make sure to include the PEP number in the pull request title; for example:
+
+PEP NNN: Mark Final
+
+Thanks!
+
+-->
+
+
+# Mark PEP Final
+
+<!--
+
+State why the PEP should be marked Final,
+linking any relevant discussions, issues or PRs.
+
+-->
+
+
+
+## Checklist
+
+<!--
+
+This lists the key steps needed to mark a PEP as Final.
+
+You can help complete it yourself if you like
+by ticking any boxes you're sure about, like this: [x]
+If you're unsure about something, just leave it blank and we'll take a look.
+
+-->
+
+
+* [ ] Specification has been implemented in a released stable CPython version (or third-party tools, for packaging/typing topic PEPs)
+* [ ] ``Status`` changed to ``Final``
+* [ ] Canonical docs/spec moved to an appropriate place, and linked with a ``canonical-doc`` directive (or ``pypa-spec``, for packaging PEPs)
+* [ ] PEP headers and content updated with any substantial changes during the implementation phase

From b34f956d66d72b1e807365d01cf672f9af0ec74e Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Mon, 9 Jan 2023 13:40:07 -0600
Subject: [PATCH 05/13] Remove existing single PR template so new templates
 work

---
 .github/PULL_REQUEST_TEMPLATE.md | 11 -----------
 1 file changed, 11 deletions(-)
 delete mode 100644 .github/PULL_REQUEST_TEMPLATE.md

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index 8db9fc296e6..00000000000
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,11 +0,0 @@
-<!--
-
-*Please* read our Contributing Guidelines (CONTRIBUTING.rst)
-before submitting an issue or pull request to this repository,
-to make sure this repo is the appropriate venue for your proposed change.
-
-Prefix the pull request title with the PEP number; for example:
-
-PEP NNN: Summary of the changes made
-
--->

From 83c7fbcd72824056f2daad6d4e854208a93b21d8 Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Fri, 13 Jan 2023 18:59:07 -0600
Subject: [PATCH 06/13] Apply suggestions from code review by Petr

Co-authored-by: Petr Viktorin <encukou@gmail.com>
---
 .../accept-reject-pep.md                      | 17 ++------
 .../PULL_REQUEST_TEMPLATE/mark-pep-final.md   | 20 +++------
 .github/PULL_REQUEST_TEMPLATE/new-pep.md      | 43 ++++++++-----------
 3 files changed, 27 insertions(+), 53 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
index b3f55308e1e..694d59d31cb 100644
--- a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
@@ -22,18 +22,7 @@ Thanks!
 
 <!--
 
-Link to the official acceptance/rejection message
-by the Steering Council/PEP Delegate on the PEP's discussion thread.
-
--->
-
-
-
-## Checklist
-
-<!--
-
-This lists the key steps needed to mark a PEP as Accepted/Rejected.
+This checklist contains the key changes to mark a PEP as Accepted/Rejected.
 
 You can help complete it yourself if you like
 by ticking any boxes you're sure about, like this: [x]
@@ -46,5 +35,5 @@ If you're unsure about anything, just leave it blank and we'll take a look.
 * [ ] SC/PEP Delegate has formally accepted/rejected the PEP and posted to the ``Discussions-To`` thread
 * [ ] ``Status`` changed to ``Accepted``/``Rejected``
 * [ ] ``Resolution`` link points directly to SC/PEP Delegate official acceptance/rejected post
-* [ ] Acceptance/rejection notice added, if the SC/PEP delegate had any major conditions or critical commentary (and any changes made accordingly)
-* [ ] ``Discussions-To``, ``Post-History` and ``Python-Version`` complete and up to date
+* [ ] Acceptance/rejection notice added, if the SC/PEP delegate had major conditions or comments
+* [ ] ``Discussions-To``, ``Post-History`` and ``Python-Version`` up to date
diff --git a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
index cb049aa2f1f..9331eb5b118 100644
--- a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
+++ b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
@@ -22,18 +22,7 @@ Thanks!
 
 <!--
 
-State why the PEP should be marked Final,
-linking any relevant discussions, issues or PRs.
-
--->
-
-
-
-## Checklist
-
-<!--
-
-This lists the key steps needed to mark a PEP as Final.
+This checklist contains the key changes needed to mark a PEP as Final.
 
 You can help complete it yourself if you like
 by ticking any boxes you're sure about, like this: [x]
@@ -42,7 +31,8 @@ If you're unsure about something, just leave it blank and we'll take a look.
 -->
 
 
-* [ ] Specification has been implemented in a released stable CPython version (or third-party tools, for packaging/typing topic PEPs)
+* [ ] Final implementation has been merged (including tests and documentation)
+* [ ] PEP matches the final implementation
+* [ ] Any substantial changes since the accepted version approved by the SC/PEP delegate
 * [ ] ``Status`` changed to ``Final``
-* [ ] Canonical docs/spec moved to an appropriate place, and linked with a ``canonical-doc`` directive (or ``pypa-spec``, for packaging PEPs)
-* [ ] PEP headers and content updated with any substantial changes during the implementation phase
+* [ ] Canonical docs/spec linked with a ``canonical-doc`` directive (or ``pypa-spec``, for packaging PEPs)
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-pep.md b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
index 16fee30ee41..dd9856de976 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
@@ -1,6 +1,6 @@
 ---
-name: New PEP
-about: Submit a new draft PEP for consideration
+name: New Standards Track PEP
+about: Submit a new draft Standards Track PEP for consideration
 labels: "new-pep"
 ---
 
@@ -27,21 +27,9 @@ Thanks!
 
 <!--
 
-Briefly describe your new PEP here, and anything else we should know.
-Be sure to link to any previous discussions or issues motivating/drafting it.
-
--->
-
-
-
-## Checklist
-
-<!--
-
-You should use the following as a guide when double-checking your PEP,
+You can use the following checklist when double-checking your PEP,
 and you can help complete some of it yourself if you like
 by ticking any boxes you're sure about, like this: [x]
-
 If you're unsure about anything, just leave it blank and we'll take a look.
 
 -->
@@ -50,13 +38,21 @@ If you're unsure about anything, just leave it blank and we'll take a look.
 
 ### Content requirements
 
-* [ ] PEP topic [discussed in a suitable venue](https://peps.python.org/pep-0001/#start-with-an-idea-for-python) and general agreement that a PEP is appropriate
-* [ ] Content is reasonably sound, complete and makes at least basic technical sense
-* [ ] Abstract and Copyright sections completed, with the required wording in the latter
-* [ ] [Suggested sections](https://peps.python.org/pep-0012/#suggested-sections) included (unless not applicable)
-* [ ] Title clearly, accurately and concisely describes the content
-* [ ] Prose is intelligible and generally free of basic grammar and syntax errors, at least to the degree they significantly detract from understanding
-* [ ] Code is in code blocks, well-formatted (PEP 7/PEP 8) and has the right [lexer name](https://pygments.org/docs/lexers/) if non-Python (or ``text``)
+* [ ] PEP topic [discussed in a suitable venue](https://peps.python.org/pep-0001/#start-with-an-idea-for-python) with general agreement that a PEP is appropriate
+* [ ] [Required and suggested sections](https://peps.python.org/pep-0012/#suggested-sections) included (unless not applicable)
+    * [ ] Abstract (required; first section)~
+    * [ ] Motivation
+    * [ ] Rationale
+    * [ ] Specification
+    * [ ] Backwards Compatibility
+    * [ ] Security Implications
+    * [ ] How to Teach This
+    * [ ] Reference Implementation
+    * [ ] Rejected Ideas
+    * [ ] Open Issues
+    * [ ] Copyright (required with exact wording; last section)
+* [ ] Title clearly, accurately and concisely describes the content in 79 characters or less
+* [ ] Code is well-formatted (PEP 7/PEP 8) and is in [code blocks, with the right lexer name](https://peps.python.org/pep-0012/#literal-blocks) if non-Python
 * [ ] Any project stated in the PEP as supporting/endorsing benefiting from it confirms such
 
 
@@ -64,8 +60,7 @@ If you're unsure about anything, just leave it blank and we'll take a look.
 
 * [ ] Filename in the correct format (``pep-NNNN.rst``)
 * [ ] ``PEP``, ``Title``, ``Author``, ``Status`` (``Draft``), ``Type`` and ``Created`` headers filled out correctly
-* [ ] ``PEP-Delegate``, ``Requires``, ``Python-Version`` and ``Replaces`` filled out if appropriate
-* [ ] ``Sponsor`` listed and approves if not authored by a core dev or PEP editor
+* [ ] ``Sponsor``, ``PEP-Delegate``, ``Requires``, ``Python-Version`` and ``Replaces`` completed if appropriate
 * [ ] PEP builds with no warnings, CI checks pass and content displays as intended in the rendered preview
 * [ ] PEP number assigned by the PEP editors and filename & ``PEP`` header updated accordingly
 * [ ] Sponsor/author(s) that are core devs/PEP editors added to ``.github/CODEOWNERS`` for the PEP

From 639af1b90e6c10c63d85de6c4944efb15eb7282c Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Fri, 13 Jan 2023 20:14:41 -0600
Subject: [PATCH 07/13] Further revise PR checklists to clarity Standards Track
 vs other PEPs

---
 .../accept-reject-pep.md                      |  2 +-
 .../PULL_REQUEST_TEMPLATE/mark-pep-final.md   |  8 ++--
 .github/PULL_REQUEST_TEMPLATE/new-pep.md      | 40 ++++++++++---------
 3 files changed, 26 insertions(+), 24 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
index 694d59d31cb..e3827ac7846 100644
--- a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
@@ -1,6 +1,6 @@
 ---
 name: Accept/Reject PEP
-about: Mark a draft PEP as accepted or rejected
+about: Mark a draft Standards Track PEP as accepted or rejected
 ---
 
 <!--
diff --git a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
index 9331eb5b118..3e1bf5ab2fa 100644
--- a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
+++ b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
@@ -1,6 +1,6 @@
 ---
 name: Mark PEP Final
-about: Mark an Accepted PEP as Final
+about: Mark an Accepted Standards Track PEP as Final
 ---
 
 <!--
@@ -22,7 +22,7 @@ Thanks!
 
 <!--
 
-This checklist contains the key changes needed to mark a PEP as Final.
+This checklist contains the key changes needed to mark a Standards Track PEP Final.
 
 You can help complete it yourself if you like
 by ticking any boxes you're sure about, like this: [x]
@@ -31,8 +31,8 @@ If you're unsure about something, just leave it blank and we'll take a look.
 -->
 
 
-* [ ] Final implementation has been merged (including tests and documentation)
+* [ ] Final implementation has been merged (including tests and docs)
 * [ ] PEP matches the final implementation
 * [ ] Any substantial changes since the accepted version approved by the SC/PEP delegate
-* [ ] ``Status`` changed to ``Final``
+* [ ] ``Status`` changed to ``Final`` (and ``Python-Version`` is correct)
 * [ ] Canonical docs/spec linked with a ``canonical-doc`` directive (or ``pypa-spec``, for packaging PEPs)
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-pep.md b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
index dd9856de976..e08dcb6d68e 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
@@ -1,6 +1,6 @@
 ---
-name: New Standards Track PEP
-about: Submit a new draft Standards Track PEP for consideration
+name: New PEP
+about: Submit a new draft PEP
 labels: "new-pep"
 ---
 
@@ -32,15 +32,29 @@ and you can help complete some of it yourself if you like
 by ticking any boxes you're sure about, like this: [x]
 If you're unsure about anything, just leave it blank and we'll take a look.
 
+If your PEP is not Standards Track, remove the corresponding section.
+
 -->
 
+## Basic requirements (all PEP Types)
+
 * [ ] File created from the [latest PEP template](https://github.com/python/peps/blob/main/pep-0012/pep-NNNN.rst?plain=1)
+* [ ] PEP has next available number, with filename (``pep-NNNN.rst``) and ``PEP`` header set accordingly
+* [ ] Title clearly, accurately and concisely describes the content in 79 characters or less
+* [ ] ``PEP``, ``Title``, ``Author``, ``Status`` (``Draft``), ``Type`` and ``Created`` headers filled out correctly
+* [ ] ``Sponsor``, ``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](https://peps.python.org/pep-0012/#literal-blocks) 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
+
 
-### Content requirements
+## Standards Track requirements
 
 * [ ] PEP topic [discussed in a suitable venue](https://peps.python.org/pep-0001/#start-with-an-idea-for-python) with general agreement that a PEP is appropriate
-* [ ] [Required and suggested sections](https://peps.python.org/pep-0012/#suggested-sections) included (unless not applicable)
-    * [ ] Abstract (required; first section)~
+* [ ] [Suggested sections](https://peps.python.org/pep-0012/#suggested-sections) included (unless not applicable)
     * [ ] Motivation
     * [ ] Rationale
     * [ ] Specification
@@ -50,18 +64,6 @@ If you're unsure about anything, just leave it blank and we'll take a look.
     * [ ] Reference Implementation
     * [ ] Rejected Ideas
     * [ ] Open Issues
-    * [ ] Copyright (required with exact wording; last section)
-* [ ] Title clearly, accurately and concisely describes the content in 79 characters or less
-* [ ] Code is well-formatted (PEP 7/PEP 8) and is in [code blocks, with the right lexer name](https://peps.python.org/pep-0012/#literal-blocks) if non-Python
-* [ ] Any project stated in the PEP as supporting/endorsing benefiting from it confirms such
-
-
-### Technical requirements
-
-* [ ] Filename in the correct format (``pep-NNNN.rst``)
-* [ ] ``PEP``, ``Title``, ``Author``, ``Status`` (``Draft``), ``Type`` and ``Created`` headers filled out correctly
-* [ ] ``Sponsor``, ``PEP-Delegate``, ``Requires``, ``Python-Version`` and ``Replaces`` completed if appropriate
-* [ ] PEP builds with no warnings, CI checks pass and content displays as intended in the rendered preview
-* [ ] PEP number assigned by the PEP editors and filename & ``PEP`` header updated accordingly
-* [ ] Sponsor/author(s) that are core devs/PEP editors added to ``.github/CODEOWNERS`` for the PEP
+* [ ] ``Python-Version`` set to valid (pre-beta) future Python version
+* [ ] Any project stated in the PEP as supporting/endorsing/benefiting from it confirms such
 * [ ] Right before or after initial merging, [PEP discussion thread](https://peps.python.org/pep-0001/#discussing-a-pep) created and linked to in ``Discussions-To`` and ``Post-History``

From ecc73f27ad4ad79b3025d7e0a6ced7a7c0238e76 Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Tue, 17 Jan 2023 12:56:51 -0600
Subject: [PATCH 08/13] Further trim down template comments & move to checklist
 items

---
 .../accept-reject-pep.md                      | 20 ++---------------
 .../PULL_REQUEST_TEMPLATE/mark-pep-final.md   | 20 ++---------------
 .github/PULL_REQUEST_TEMPLATE/new-pep.md      | 22 ++-----------------
 3 files changed, 6 insertions(+), 56 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
index e3827ac7846..f4a848de02b 100644
--- a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
@@ -3,28 +3,11 @@ name: Accept/Reject PEP
 about: Mark a draft Standards Track PEP as accepted or rejected
 ---
 
-<!--
-
-See PEP 1 for more details about the PEP review and resolution process:
-
-https://peps.python.org/pep-0001/#pep-review-resolution
-
-Make sure to include the PEP number in the pull request title; for example:
-
-PEP NNN: Mark as Accepted/Rejected
-
-Thanks!
-
--->
-
-
 # Accept/Reject PEP
 
 <!--
 
-This checklist contains the key changes to mark a PEP as Accepted/Rejected.
-
-You can help complete it yourself if you like
+You can help complete the following checklist yourself if you like
 by ticking any boxes you're sure about, like this: [x]
 
 If you're unsure about anything, just leave it blank and we'll take a look.
@@ -33,6 +16,7 @@ If you're unsure about anything, just leave it blank and we'll take a look.
 
 
 * [ ] SC/PEP Delegate has formally accepted/rejected the PEP and posted to the ``Discussions-To`` thread
+* [ ] Pull request title in appropriate format (``PEP 123: Mark as accepted``)
 * [ ] ``Status`` changed to ``Accepted``/``Rejected``
 * [ ] ``Resolution`` link points directly to SC/PEP Delegate official acceptance/rejected post
 * [ ] Acceptance/rejection notice added, if the SC/PEP delegate had major conditions or comments
diff --git a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
index 3e1bf5ab2fa..b37d4187b56 100644
--- a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
+++ b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
@@ -3,28 +3,11 @@ name: Mark PEP Final
 about: Mark an Accepted Standards Track PEP as Final
 ---
 
-<!--
-
-See PEP 1 for more about the PEP lifecycle and when one is considered Final:
-
-https://peps.python.org/pep-0001/#pep-review-resolution
-
-Make sure to include the PEP number in the pull request title; for example:
-
-PEP NNN: Mark Final
-
-Thanks!
-
--->
-
-
 # Mark PEP Final
 
 <!--
 
-This checklist contains the key changes needed to mark a Standards Track PEP Final.
-
-You can help complete it yourself if you like
+You can help complete the following checklist yourself if you like
 by ticking any boxes you're sure about, like this: [x]
 If you're unsure about something, just leave it blank and we'll take a look.
 
@@ -34,5 +17,6 @@ If you're unsure about something, just leave it blank and we'll take a look.
 * [ ] Final implementation has been merged (including tests and docs)
 * [ ] PEP matches the final implementation
 * [ ] Any substantial changes since the accepted version approved by the SC/PEP delegate
+* [ ] Pull request title in appropriate format (``PEP 123: Mark Final``)
 * [ ] ``Status`` changed to ``Final`` (and ``Python-Version`` is correct)
 * [ ] Canonical docs/spec linked with a ``canonical-doc`` directive (or ``pypa-spec``, for packaging PEPs)
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-pep.md b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
index e08dcb6d68e..b288533b20f 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
@@ -4,25 +4,6 @@ about: Submit a new draft PEP
 labels: "new-pep"
 ---
 
-<!--
-
-Please read and follow PEP 1 and PEP 12 before submitting a new PEP:
-
-https://peps.python.org/pep-0001/#submitting-a-pep
-
-https://peps.python.org/pep-0012/#how-to-use-this-template
-
-Make sure to include the PEP number in the pull request title; for example:
-
-PEP 9999: <Title of PEP>
-
-See our Contributing Guidelines (CONTRIBUTING.rst) for more information.
-
-Thanks!
-
--->
-
-
 # New PEP
 
 <!--
@@ -38,8 +19,9 @@ If your PEP is not Standards Track, remove the corresponding section.
 
 ## Basic requirements (all PEP Types)
 
+* [ ] Read and followed [PEP 1](https://peps.python.org/1) & [PEP 12](https://peps.python.org/12)
 * [ ] File created from the [latest PEP template](https://github.com/python/peps/blob/main/pep-0012/pep-NNNN.rst?plain=1)
-* [ ] PEP has next available number, with filename (``pep-NNNN.rst``) and ``PEP`` header set accordingly
+* [ ] 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
 * [ ] ``PEP``, ``Title``, ``Author``, ``Status`` (``Draft``), ``Type`` and ``Created`` headers filled out correctly
 * [ ] ``Sponsor``, ``PEP-Delegate``, ``Topic``, ``Requires`` and ``Replaces`` headers completed if appropriate

From a8aebdb978df6a5ea599544e5f26af0f8401f283 Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Wed, 18 Jan 2023 19:18:08 -0600
Subject: [PATCH 09/13] Add new Modify PEP template and simplify existing
 further

---
 .../PULL_REQUEST_TEMPLATE/accept-reject-pep.md    |  3 ---
 .github/PULL_REQUEST_TEMPLATE/mark-pep-final.md   |  3 ---
 .github/PULL_REQUEST_TEMPLATE/modify-pep.md       | 15 +++++++++++++++
 .github/PULL_REQUEST_TEMPLATE/new-pep.md          |  2 --
 .github/PULL_REQUEST_TEMPLATE/other.md            | 15 +++------------
 5 files changed, 18 insertions(+), 20 deletions(-)
 create mode 100644 .github/PULL_REQUEST_TEMPLATE/modify-pep.md

diff --git a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
index f4a848de02b..e1f9918303c 100644
--- a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
@@ -6,15 +6,12 @@ about: Mark a draft Standards Track PEP as accepted or rejected
 # Accept/Reject PEP
 
 <!--
-
 You can help complete the following checklist yourself if you like
 by ticking any boxes you're sure about, like this: [x]
 
 If you're unsure about anything, just leave it blank and we'll take a look.
-
 -->
 
-
 * [ ] SC/PEP Delegate has formally accepted/rejected the PEP and posted to the ``Discussions-To`` thread
 * [ ] Pull request title in appropriate format (``PEP 123: Mark as accepted``)
 * [ ] ``Status`` changed to ``Accepted``/``Rejected``
diff --git a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
index b37d4187b56..b8c44f08e33 100644
--- a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
+++ b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
@@ -6,14 +6,11 @@ about: Mark an Accepted Standards Track PEP as Final
 # Mark PEP Final
 
 <!--
-
 You can help complete the following checklist yourself if you like
 by ticking any boxes you're sure about, like this: [x]
 If you're unsure about something, just leave it blank and we'll take a look.
-
 -->
 
-
 * [ ] Final implementation has been merged (including tests and docs)
 * [ ] PEP matches the final implementation
 * [ ] Any substantial changes since the accepted version approved by the SC/PEP delegate
diff --git a/.github/PULL_REQUEST_TEMPLATE/modify-pep.md b/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
new file mode 100644
index 00000000000..30a729c0025
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
@@ -0,0 +1,15 @@
+---
+name: Update/modify PEP
+about: Add to or change an existing PEP
+---
+
+<!--
+**Please** read our Contributing Guidelines (CONTRIBUTING.rst)
+to make sure this repo is the right place for your proposed change. Thanks!
+-->
+
+* Change is either:
+    * [ ] To a Draft PEP
+    * [ ] To an Accepted or Final PEP, with Steering Council approval
+    * [ ] Resolving a purely technical or editorial issue
+* [ ] PR title prefixed with PEP number (e.g. ``PEP 123: Summary of changes``)
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-pep.md b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
index b288533b20f..92073ef7fd8 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
@@ -7,14 +7,12 @@ labels: "new-pep"
 # New PEP
 
 <!--
-
 You can use the following checklist when double-checking your PEP,
 and you can help complete some of it yourself if you like
 by ticking any boxes you're sure about, like this: [x]
 If you're unsure about anything, just leave it blank and we'll take a look.
 
 If your PEP is not Standards Track, remove the corresponding section.
-
 -->
 
 ## Basic requirements (all PEP Types)
diff --git a/.github/PULL_REQUEST_TEMPLATE/other.md b/.github/PULL_REQUEST_TEMPLATE/other.md
index b8a116e9f53..cfc11d00882 100644
--- a/.github/PULL_REQUEST_TEMPLATE/other.md
+++ b/.github/PULL_REQUEST_TEMPLATE/other.md
@@ -1,18 +1,9 @@
 ---
 name: Other
-about: Any PR that doesn't fall in the other categories
+about: Infra or meta change not falling in another category
 ---
 
 <!--
-
-*Please* read our Contributing Guidelines (CONTRIBUTING.rst)
-before submitting an issue or pull request to this repository,
-to make sure this repo is the appropriate venue for your proposed change.
-
-Prefix the pull request title with the PEP number; for example:
-
-PEP NNN: Summary of the changes made
-
-Thanks!
-
+**Please** read our Contributing Guidelines (CONTRIBUTING.rst)
+to make sure this repo is the right place for your proposed change. Thanks!
 -->

From 1a9c8de5ffa4962386604016b3461948eef7850e Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Mon, 23 Jan 2023 03:12:07 -0600
Subject: [PATCH 10/13] Further refine PEP change ording per review feedback

---
 .github/PULL_REQUEST_TEMPLATE/modify-pep.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/modify-pep.md b/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
index 30a729c0025..b532c857e12 100644
--- a/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
@@ -11,5 +11,5 @@ to make sure this repo is the right place for your proposed change. Thanks!
 * Change is either:
     * [ ] To a Draft PEP
     * [ ] To an Accepted or Final PEP, with Steering Council approval
-    * [ ] Resolving a purely technical or editorial issue
+    * [ ] To fix an editorial issue (markup, typo, link, header, etc)
 * [ ] PR title prefixed with PEP number (e.g. ``PEP 123: Summary of changes``)

From 84b7ac5a38958d6c31ed91e527a1e6d52f6e694d Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Mon, 23 Jan 2023 03:17:08 -0600
Subject: [PATCH 11/13] Add title placeholders to PR templates

---
 .github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md | 3 ++-
 .github/PULL_REQUEST_TEMPLATE/mark-pep-final.md    | 1 +
 .github/PULL_REQUEST_TEMPLATE/modify-pep.md        | 1 +
 .github/PULL_REQUEST_TEMPLATE/new-pep.md           | 1 +
 4 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
index e1f9918303c..fdefc08d784 100644
--- a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
@@ -1,6 +1,7 @@
 ---
 name: Accept/Reject PEP
 about: Mark a draft Standards Track PEP as accepted or rejected
+title: PEP NNN: Mark as Accepted
 ---
 
 # Accept/Reject PEP
@@ -13,7 +14,7 @@ If you're unsure about anything, just leave it blank and we'll take a look.
 -->
 
 * [ ] SC/PEP Delegate has formally accepted/rejected the PEP and posted to the ``Discussions-To`` thread
-* [ ] Pull request title in appropriate format (``PEP 123: Mark as accepted``)
+* [ ] Pull request title in appropriate format (``PEP 123: Mark as Accepted``)
 * [ ] ``Status`` changed to ``Accepted``/``Rejected``
 * [ ] ``Resolution`` link points directly to SC/PEP Delegate official acceptance/rejected post
 * [ ] Acceptance/rejection notice added, if the SC/PEP delegate had major conditions or comments
diff --git a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
index b8c44f08e33..78cb5f5dd2d 100644
--- a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
+++ b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
@@ -1,6 +1,7 @@
 ---
 name: Mark PEP Final
 about: Mark an Accepted Standards Track PEP as Final
+title: PEP NNN: Mark Final
 ---
 
 # Mark PEP Final
diff --git a/.github/PULL_REQUEST_TEMPLATE/modify-pep.md b/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
index b532c857e12..8f6ac98a07e 100644
--- a/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
@@ -1,6 +1,7 @@
 ---
 name: Update/modify PEP
 about: Add to or change an existing PEP
+title: PEP NNN: Description of change
 ---
 
 <!--
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-pep.md b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
index 92073ef7fd8..c771bb2cfdb 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
@@ -1,6 +1,7 @@
 ---
 name: New PEP
 about: Submit a new draft PEP
+title: PEP NNN: Title of PEP
 labels: "new-pep"
 ---
 

From a8538d9fd90caf4a3ac78d3232ba60e386343146 Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Mon, 23 Jan 2023 04:06:40 -0600
Subject: [PATCH 12/13] Quote YAML title fields in PR templates

Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
---
 .github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md | 2 +-
 .github/PULL_REQUEST_TEMPLATE/mark-pep-final.md    | 2 +-
 .github/PULL_REQUEST_TEMPLATE/modify-pep.md        | 2 +-
 .github/PULL_REQUEST_TEMPLATE/new-pep.md           | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
index fdefc08d784..4bdbb0a6d21 100644
--- a/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/accept-reject-pep.md
@@ -1,7 +1,7 @@
 ---
 name: Accept/Reject PEP
 about: Mark a draft Standards Track PEP as accepted or rejected
-title: PEP NNN: Mark as Accepted
+title: "PEP NNN: Mark as Accepted"
 ---
 
 # Accept/Reject PEP
diff --git a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
index 78cb5f5dd2d..41f0a57ec44 100644
--- a/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
+++ b/.github/PULL_REQUEST_TEMPLATE/mark-pep-final.md
@@ -1,7 +1,7 @@
 ---
 name: Mark PEP Final
 about: Mark an Accepted Standards Track PEP as Final
-title: PEP NNN: Mark Final
+title: "PEP NNN: Mark Final"
 ---
 
 # Mark PEP Final
diff --git a/.github/PULL_REQUEST_TEMPLATE/modify-pep.md b/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
index 8f6ac98a07e..c04c4e78b54 100644
--- a/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/modify-pep.md
@@ -1,7 +1,7 @@
 ---
 name: Update/modify PEP
 about: Add to or change an existing PEP
-title: PEP NNN: Description of change
+title: "PEP NNN: Description of change"
 ---
 
 <!--
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-pep.md b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
index c771bb2cfdb..f0bf3e18584 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
@@ -1,7 +1,7 @@
 ---
 name: New PEP
 about: Submit a new draft PEP
-title: PEP NNN: Title of PEP
+title: "PEP NNN: Title of PEP"
 labels: "new-pep"
 ---
 

From a0b77a2a05529a2e2b21f4c250f828fe76cb1763 Mon Sep 17 00:00:00 2001
From: "C.A.M. Gerlach" <CAM.Gerlach@Gerlach.CAM>
Date: Mon, 30 Jan 2023 23:32:46 -0600
Subject: [PATCH 13/13] Add back dedicated Author/Sponsor item to new PEP
 checklist

---
 .github/PULL_REQUEST_TEMPLATE/new-pep.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/new-pep.md b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
index f0bf3e18584..19f230e3410 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-pep.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-pep.md
@@ -23,7 +23,8 @@ If your PEP is not Standards Track, remove the corresponding section.
 * [ ] 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
 * [ ] ``PEP``, ``Title``, ``Author``, ``Status`` (``Draft``), ``Type`` and ``Created`` headers filled out correctly
-* [ ] ``Sponsor``, ``PEP-Delegate``, ``Topic``, ``Requires`` and ``Replaces`` headers completed if appropriate
+* [ ] ``PEP-Delegate``, ``Topic``, ``Requires`` and ``Replaces`` headers completed if appropriate
+* [ ] Core dev/PEP editor listed as author or sponsor, and formally confirmed their approval
 * [ ] Required sections included
     * [ ] Abstract (first section)
     * [ ] Copyright (last section; exact wording from template required)

<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
<html xmlns='http://www.w3.org/1999/xhtml'>
<head>
<title>pFad - Phonifier reborn</title>
<meta http-equiv='Content-Type' content='text/html; charset=utf-8' />
</head>
<body>
<h1>Pfad - The Proxy pFad of &#169; 2024 Garber Painting. All rights reserved.</h1>


<!-- Disclaimer -->
<p>Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.</p>
<br>
<p>Alternative Proxies:</p><p><a href="http://rainy.clevelandohioweatherforecast.com/php-proxy/index.php?q=https://patch-diff.githubusercontent.com/raw/python/peps/pull/2956.patch" target="_blank">Alternative Proxy</a></p><p><a href="http://rainy.clevelandohioweatherforecast.com/pFad/index.php?u=https://patch-diff.githubusercontent.com/raw/python/peps/pull/2956.patch" target="_blank">pFad Proxy</a></p><p><a href="http://rainy.clevelandohioweatherforecast.com/pFad/v3index.php?u=https://patch-diff.githubusercontent.com/raw/python/peps/pull/2956.patch" target="_blank">pFad v3 Proxy</a></p><p><a href="http://rainy.clevelandohioweatherforecast.com/pFad/v4index.php?u=https://patch-diff.githubusercontent.com/raw/python/peps/pull/2956.patch" target="_blank">pFad v4 Proxy</a></p></body>
</html>