Merge branch 'main' into konsti/pep-815-final

konstin · web-flow · commit ea89e6fb58bf · 2026-02-04T09:22:33.000+01:00
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -697,6 +697,7 @@ peps/pep-0817/     @warsaw @dstufft
 # ...
 peps/pep-0819.rst  @emmatyping
 peps/pep-0820.rst  @encukou
+peps/pep-0821.rst  @JelleZijlstra
 peps/pep-0822.rst  @methane
 # ...
 peps/pep-2026.rst  @hugovk
diff --git a/.github/PULL_REQUEST_TEMPLATE/Add a new PEP.md b/.github/PULL_REQUEST_TEMPLATE/Add a new PEP.md
@@ -37,6 +37,9 @@ If your PEP is not Standards Track, remove the corresponding section.
     * [ ] Reference Implementation
     * [ ] Rejected Ideas
     * [ ] Open Issues
+    * [ ] Acknowledgements
+    * [ ] Footnotes
+    * [ ] Change History
 * [ ] ``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](https://peps.python.org/pep-0001/#discussing-a-pep) created and linked to in ``Discussions-To`` and ``Post-History``
diff --git a/peps/pep-0001.rst b/peps/pep-0001.rst
@@ -581,7 +581,18 @@ Each PEP should have the following parts/sections:
 13. Footnotes -- A collection of footnotes cited in the PEP, and
     a place to list non-inline hyperlink targets.
 
-14. Copyright/license -- Each new PEP must be placed under a dual license of
+Change History -- A summary of major changes the PEP has undergone, based on
+    discussions and feedback. Think of this as a "changelog" or "release notes"
+    for the PEP.  In general, whenever you update the ``Post-History`` header
+    for major changes, add a new bullet item in newest-first (i.e. reverse
+    chronological) order, using the same ``DD-MMM-YYYY`` format, with
+    sub-bullets summarizing the changes. You can consider linking this to the
+    same link as the ``Post-History`` link.  This isn't mandatory, so it's left
+    to the PEP author's discretion, but such a section can be helpful for those
+    following along to understand the evolution of your PEP.  Here is :pep:`an
+    example <694#change-history>`.
+
+15. Copyright/license -- Each new PEP must be placed under a dual license of
     public domain and CC0-1.0-Universal_ (see this PEP for an example).
 
 
@@ -876,6 +887,14 @@ Footnotes
 .. _Contributing Guide: https://github.com/python/peps/blob/main/CONTRIBUTING.rst
 
 
+Change History
+==============
+
+* 2026-02-02
+
+  * Added an optional ``Change History`` section for PEPs, for summarizing changes when updating the
+    ``Post-History`` header.
+
 Copyright
 =========
 
diff --git a/peps/pep-0012.rst b/peps/pep-0012.rst
@@ -100,8 +100,8 @@ directions below.
   feature is described in a Final PEP.
 
 - Change the Created header to today's date.  Be sure to follow the
-  format carefully: it must be in ``dd-mmm-yyyy`` format, where the
-  ``mmm`` is the 3 English letter month abbreviation, i.e. one of Jan,
+  format carefully: it must be in ``DD-MMM-YYYY`` format, where the
+  ``MMM`` is the three-letter English month abbreviation, i.e. one of Jan,
   Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.
 
 - For Standards Track PEPs, after the Created header, add a
@@ -122,7 +122,7 @@ directions below.
 - Post-History can be 'Pending' for now; you'll add dates and corresponding links
   to this header each time you post your PEP to the designated discussion forum
   (and update the Discussions-To header with said link, as above).
-  For each thread, use the date (in the ``dd-mmm-yyy`` format) as the
+  For each thread, use the date (in the ``DD-MMM-YYYY`` format) as the
   linked text, and insert the URLs inline as anonymous reST `hyperlinks`_,
   with commas in between each posting.
 
diff --git a/peps/pep-0012/pep-NNNN.rst b/peps/pep-0012/pep-NNNN.rst
@@ -88,6 +88,16 @@ Footnotes
 [A collection of footnotes cited in the PEP, and a place to list non-inline hyperlink targets.]
 
 
+Change History
+==============
+
+[A summary of major changes the PEP has undergone.  Whenever you update the
+``Post-History``, add a new bullet item in newest-first (i.e. reverse
+chronological) order, using the same ``DD-MMM-YYYY`` format, with sub-bullets
+summarizing the changes.  You can use the same link for the date bullet as you
+do in the ``Post-History`` addition.]
+
+
 Copyright
 =========
 
diff --git a/peps/pep-0512.rst b/peps/pep-0512.rst
@@ -963,39 +963,12 @@ References
 .. [#tracker-plans] Wiki page for bugs.python.org feature development
    (https://wiki.python.org/moin/TrackerDevelopmentPlanning)
 
-.. [#black-knight-sketch] The "Black Knight" sketch from "Monty Python and the Holy Grail"
-   (https://www.youtube.com/watch?v=dhRUe-gz690)
-
-.. [#bridge-of-death-sketch] The "Bridge of Death" sketch from "Monty Python and the Holy Grail"
-   (https://www.youtube.com/watch?v=cV0tCphFMr8)
-
-.. [#holy-grail] "Monty Python and the Holy Grail" sketches
-   (https://www.youtube.com/playlist?list=PL-Qryc-SVnnu1MvN3r94Y9atpaRuIoGmp)
-
-.. [#killer-rabbit-sketch] "Killer rabbit" sketch from "Monty Python and the Holy Grail"
-   (https://www.youtube.com/watch?v=Nvs5pqf-DMA&list=PL-Qryc-SVnnu1MvN3r94Y9atpaRuIoGmp&index=11)
-
-.. [#french-taunter-sketch] "French Taunter" from "Monty Python and the Holy Grail"
-   (https://www.youtube.com/watch?v=A8yjNbcKkNY&list=PL-Qryc-SVnnu1MvN3r94Y9atpaRuIoGmp&index=13)
-
-.. [#constitutional-peasants-sketch] "Constitutional Peasants" from "Monty Python and the Holy Grail"
-   (https://www.youtube.com/watch?v=JvKIWjnEPNY&list=PL-Qryc-SVnnu1MvN3r94Y9atpaRuIoGmp&index=14)
-
-.. [#ni-sketch] "Knights Who Say Ni" from "Monty Python and the Holy Grail"
-   (https://www.youtube.com/watch?v=zIV4poUZAQo&list=PL-Qryc-SVnnu1MvN3r94Y9atpaRuIoGmp&index=15)
-
 .. [#homu] Homu (http://homu.io/)
 
 .. [#zuul] Zuul (http://docs.openstack.org/infra/zuul/)
 
 .. [#travis] Travis (https://travis-ci.org/)
 
-.. [#codeship] Codeship (https://codeship.com/)
-
-.. [#coverage] coverage.py (https://pypi.python.org/pypi/coverage)
-
-.. [#coveralls] Coveralls (https://coveralls.io/)
-
 .. [#codecov] Codecov (https://codecov.io/)
 
 .. [#pypatcher] Pypatcher (https://github.com/kushaldas/pypatcher)
diff --git a/peps/pep-0719.rst b/peps/pep-0719.rst
@@ -75,10 +75,10 @@ Actual:
 - 3.13.9: Tuesday, 2025-10-14
 - 3.13.10: Tuesday, 2025-12-02
 - 3.13.11: Friday, 2025-12-05
+- 3.13.12: Tuesday, 2026-02-03
 
 Expected:
 
-- 3.13.12: Tuesday, 2026-02-03
 - 3.13.13: Tuesday, 2026-04-07
 - 3.13.14: Tuesday, 2026-06-09
 - 3.13.15: Tuesday, 2026-08-04
diff --git a/peps/pep-0745.rst b/peps/pep-0745.rst
@@ -66,10 +66,10 @@ Actual:
 
 - 3.14.1: Tuesday, 2025-12-02
 - 3.14.2: Friday, 2025-12-05
+- 3.14.3: Tuesday, 2026-02-03
 
 Expected:
 
-- 3.14.3: Tuesday, 2026-02-03
 - 3.14.4: Tuesday, 2026-04-07
 - 3.14.5: Tuesday, 2026-06-09
 - 3.14.6: Tuesday, 2026-08-04
diff --git a/peps/pep-0820.rst b/peps/pep-0820.rst
diff --git a/peps/pep-0821.rst b/peps/pep-0821.rst
diff --git a/release_management/python-releases.toml b/release_management/python-releases.toml
