Merge branch 'main' into pep-694-staged-releases-legacy-entry

Author: warsaw

.github/CODEOWNERS

@@ -713,8 +713,11 @@ peps/pep-0835.rst  @ilevkivskyi
 peps/pep-0836.rst  @savannahostrowski @Fidget-Spinner @brandtbucher
 peps/pep-0837.rst  @serhiy-storchaka
 peps/pep-0838.rst  @AlexWaygood
+peps/pep-0839.rst  @corona10
 peps/pep-0840.rst  @jeremyhylton @gvanrossum
+peps/pep-0841.rst  @corona10 @sobolevn
 peps/pep-0842.rst  @ZeroIntensity
+peps/pep-0844.rst  @warsaw
 # ...
 peps/pep-2026.rst  @hugovk
 # ...

.github/workflows/test.yml

@@ -30,7 +30,6 @@ jobs:
       fail-fast: false
       matrix:
         python-version:
-        - "3.10"
         - "3.11"
         - "3.12"
         - "3.13"

.pre-commit-config.yaml

@@ -53,8 +53,7 @@ repos:
       - id: black
         name: "Format with Black"
         args:
-          - '--target-version=py39'
-          - '--target-version=py310'
+          - '--target-version=py311'
         files: '^(peps/conf\.py|pep_sphinx_extensions/tests/.*)$'
 
   - repo: https://github.com/astral-sh/ruff-pre-commit

.ruff.toml

@@ -1,5 +1,5 @@
 output-format = "full"
-target-version = "py310"
+target-version = "py311"
 
 [lint]
 ignore = [

peps/pep-0001.rst

@@ -773,10 +773,10 @@ must watch the `PEP repository`_.
 
 Note that developers with write access to the `PEP repository`_ may
 handle the tasks that would normally be taken care of by the PEP editors.
-Alternately, even developers may request assistance from PEP editors by
+Alternatively, even developers may request assistance from PEP editors by
 mentioning ``@python/pep-editors`` on GitHub.
 
-For each new PEP that comes in an editor does the following:
+For each new PEP that comes in, an editor does the following:
 
 * Make sure that the PEP is either co-authored by a core developer, has a core
   developer as a sponsor, or has a sponsor specifically approved for this PEP
@@ -835,14 +835,14 @@ for changes, and correct any structure, grammar, spelling, or
 markup mistakes they see.
 
 PEP editors don't pass judgment on PEPs.  They merely do the
-administrative & editorial part (which is generally a low volume task).
+administrative and editorial part (which is generally a low volume task).
 
 Resources:
 
 * `Index of Python Enhancement Proposals <https://peps.python.org/>`_
 
 * `Following Python's Development
-  <https://devguide.python.org/communication/>`_
+  <https://devguide.python.org/developer-workflow/communication-channels/index.html>`_
 
 * `Python Developer's Guide <https://devguide.python.org/>`_
 

peps/pep-0719.rst

@@ -78,10 +78,10 @@ Actual:
 - 3.13.12: Tuesday, 2026-02-03
 - 3.13.13: Tuesday, 2026-04-07
 - 3.13.14: Wednesday, 2026-06-10
+- 3.13.15: Wednesday, 2026-08-05
 
 Expected:
 
-- 3.13.15: Tuesday, 2026-08-04
 - 3.13.16: Tuesday, 2026-10-06
   (Final regular bugfix release with binary installers)
 

peps/pep-0745.rst

@@ -71,10 +71,10 @@ Actual:
 - 3.14.5 candidate 1: Monday, 2026-05-04
 - 3.14.5: Sunday, 2026-05-10
 - 3.14.6: Wednesday, 2026-06-10
+- 3.14.7: Wednesday, 2026-08-05
 
 Expected:
 
-- 3.14.7: Tuesday, 2026-08-04
 - 3.14.8: Tuesday, 2026-10-06
 - 3.14.9: Tuesday, 2026-12-01
 - 3.14.10: Tuesday, 2027-02-02

peps/pep-0790.rst

@@ -49,10 +49,10 @@ Actual:
 - 3.15.0 beta 2: Tuesday, 2026-06-02
 - 3.15.0 beta 3: Tuesday, 2026-06-23
 - 3.15.0 beta 4: Saturday, 2026-07-18
+- 3.15.0 candidate 1: Tuesday, 2026-08-04
 
 Expected:
 
-- 3.15.0 candidate 1: Tuesday, 2026-08-04
 - 3.15.0 candidate 2: Tuesday, 2026-09-01
 - 3.15.0 final: Thursday, 2026-10-01