Merge branch 'main' into psrt-membership

Author: hugovk

.github/CODEOWNERS

@@ -679,6 +679,13 @@ peps/pep-0800.rst  @JelleZijlstra
 peps/pep-0801.rst  @warsaw
 peps/pep-0802.rst  @AA-Turner
 peps/pep-0803.rst  @encukou
+peps/pep-0804.rst  @pradyunsg
+# ...
+peps/pep-0806.rst  @JelleZijlstra
+peps/pep-0807.rst  @dstufft
+# ...
+peps/pep-0809.rst  @zooba
+peps/pep-0810.rst  @pablogsal @DinoV @Yhg1s
 peps/pep-0811.rst  @sethmlarson @gpshead
 # ...
 peps/pep-2026.rst  @hugovk

.github/workflows/lint.yml

@@ -24,7 +24,7 @@ jobs:
           persist-credentials: false
 
       - name: Set up Python 3
-        uses: actions/setup-python@v5
+        uses: actions/setup-python@v6
         with:
           python-version: "3.x"
 

.github/workflows/render.yml

@@ -32,7 +32,7 @@ jobs:
           fetch-depth: 0  # fetch all history so that last modified date-times are accurate
 
       - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v5
+        uses: actions/setup-python@v6
         with:
           python-version: ${{ matrix.python-version }}
           cache: pip

.github/workflows/test.yml

@@ -30,7 +30,6 @@ jobs:
       fail-fast: false
       matrix:
         python-version:
-        - "3.9"
         - "3.10"
         - "3.11"
         - "3.12"
@@ -47,7 +46,7 @@ jobs:
           persist-credentials: false
 
       - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v5
+        uses: actions/setup-python@v6
         with:
           python-version: ${{ matrix.python-version }}
           allow-prereleases: true

.ruff.toml

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

peps/pep-0011.rst

@@ -124,6 +124,7 @@ aarch64-pc-windows-msvc                                      Steve Dower
 arm64-apple-ios                  iOS on device               Russell Keith-Magee, Ned Deily
 arm64-apple-ios-simulator        iOS on M1 macOS simulator   Russell Keith-Magee, Ned Deily
 armv7l-unknown-linux-gnueabihf   32-bit Raspberry Pi OS, gcc Gregory P. Smith
+aarch64-unknown-linux-gnu        64-bit Raspberry Pi OS, gcc Savannah Ostrowski
 powerpc64le-unknown-linux-gnu    glibc, clang                Victor Stinner
 
                                  glibc, gcc                  Victor Stinner

peps/pep-0013.rst

@@ -347,6 +347,7 @@ History of council elections
 * December 2022: :pep:`8104`
 * December 2023: :pep:`8105`
 * December 2024: :pep:`8106`
+* December 2025: :pep:`8107`
 
 
 History of amendments

peps/pep-0101.rst

@@ -639,7 +639,7 @@ permissions.
   The script will also sign any remaining files that were not
   signed with Sigstore until this point. Again, if this happens,
   do use your ``@python.org`` address for this process. More info:
-  https://www.python.org/download/sigstore/
+  https://www.python.org/downloads/metadata/sigstore/
 
 - In case the CDN already cached a version of the Downloads page
   without the files present, you can invalidate the cache using::
@@ -648,8 +648,8 @@ permissions.
 
 - If this is a **final** release:
 
-  - Add the new version to the *Python Documentation by Version*
-    page ``https://www.python.org/doc/versions/`` and
+  - Add the new version to the `"Python documentation by version"
+    page <https://www.python.org/doc/versions/>`__ and
     remove the current version from any 'in development' section.
 
   - For 3.X.Y, edit all the previous X.Y releases' page(s) to
@@ -666,21 +666,14 @@ permissions.
       Note: Python 3.x.(y-1) has been superseded by
       `Python 3.x.y </download/releases/3.x.y/>`_.
 
-  - Update the "Current Pre-release Testing Versions web page".
-
-    There's a page that lists all the currently-in-testing versions
-    of Python:
-
-    * https://www.python.org/download/pre-releases/
-
-    Every time you make a release, one way or another you'll
-    have to update this page:
+  - Update the `"Current pre-release testing versions" page
+    <https://www.python.org/download/pre-releases/>`__.
 
     - If you're releasing a version before *3.x.0*,
-      you should add it to this page, removing the previous pre-release
+      add it to this page, removing the previous pre-release
       of version *3.x* as needed.
 
-    - If you're releasing *3.x.0 final*, you need to remove the pre-release
+    - If you're releasing *3.x.0 final*, remove the pre-release
       version from this page.
 
     This is in the "Pages" category on the Django-based website, and finding
@@ -690,15 +683,13 @@ permissions.
     page itself.  So you can simply follow the link above, click on the
     "Edit this page" link, and make your changes as needed.  How convenient!
 
-  - If appropriate, update the "Python Documentation by Version" page:
-
-    * https://www.python.org/doc/versions/
+  - If appropriate, update the `"Python documentation by version" page
+    <https://www.python.org/doc/versions/>`__.
 
     This lists all releases of Python by version number and links to their
-    static (not built daily) online documentation.  There's a list at the
-    bottom of in-development versions, which is where all alphas/betas/RCs
-    should go.  And yes you should be able to click on the link above then
-    press the shiny, exciting "Edit this page" button.
+    static (not built daily) online documentation.  There's a link at the
+    bottom to the in-development version.
+    And yes you can press the shiny, exciting "Edit this page" button.
 
 - Write the announcement on `discuss.python.org`_.  This is the
   fuzzy bit because not much can be automated.  You can use an earlier
@@ -844,7 +835,7 @@ else does them.  Some of those tasks include:
 
   * mailing lists (python-dev, python-list, python-announcements)
 
-  * Python Dev blog
+  * `Python Insider blog <https://blog.python.org>`_
 
 - Enjoy your retirement and bask in the glow of a job well done!
 

peps/pep-0351.rst

@@ -38,8 +38,8 @@ It is conceivable that third party objects also have similar mutable
 and immutable counterparts, and it would be useful to have a standard
 protocol for conversion of such objects.
 
-sets.Set objects expose a "protocol for automatic conversion to
-immutable" so that you can create sets.Sets of sets.Sets.  :pep:`218`
+``sets.Set`` objects expose a "protocol for automatic conversion to
+immutable" so that you can create ``sets.Set``'s of ``sets.Set``'s.  :pep:`218`
 deliberately dropped this feature from built-in sets.  This PEP
 advances that the feature is still useful and proposes a standard
 mechanism for its support.
@@ -48,22 +48,24 @@ mechanism for its support.
 Proposal
 ========
 
-It is proposed that a new built-in function called freeze() is added.
+It is proposed that a new built-in function called ``freeze()`` is added.
 
-If freeze() is passed an immutable object, as determined by hash() on
-that object not raising a TypeError, then the object is returned
+If ``freeze()`` is passed an immutable object, as determined by ``hash()`` on
+that object not raising a ``TypeError``, then the object is returned
 directly.
 
-If freeze() is passed a mutable object (i.e. hash() of that object
-raises a TypeError), then freeze() will call that object's
-__freeze__() method to get an immutable copy.  If the object does not
-have a __freeze__() method, then a TypeError is raised.
+If ``freeze()`` is passed a mutable object (i.e. ``hash()`` of that object
+raises a ``TypeError``), then ``freeze()`` will call that object's
+``__freeze__()`` method to get an immutable copy.  If the object does not
+have a ``__freeze__()`` method, then a ``TypeError`` is raised.
 
 
 Sample implementations
 ======================
 
-Here is a Python implementation of the freeze() built-in::
+Here is a Python implementation of the ``freeze()`` built-in:
+
+.. code-block:: python
 
     def freeze(obj):
         try:
@@ -73,9 +75,11 @@ Here is a Python implementation of the freeze() built-in::
             freezer = getattr(obj, '__freeze__', None)
             if freezer:
                 return freezer()
-            raise TypeError('object is not freezable')``
+            raise TypeError('object is not freezable')
+
+Here are some code samples which show the intended semantics:
 
-Here are some code samples which show the intended semantics::
+.. code-block:: python
 
     class xset(set):
         def __freeze__(self):
@@ -104,6 +108,8 @@ Here are some code samples which show the intended semantics::
         def __freeze__(self):
             return imdict(self)
 
+.. code-block:: python-console
+
     >>> s = set([1, 2, 3])
     >>> {s: 4}
     Traceback (most recent call last):
@@ -140,9 +146,9 @@ Reference implementation
 ========================
 
 Patch 1335812_ provides the C implementation of this feature.  It adds the
-freeze() built-in, along with implementations of the __freeze__()
+``freeze()`` built-in, along with implementations of the ``__freeze__()``
 method for lists and sets.  Dictionaries are not easily freezable in
-current Python, so an implementation of dict.__freeze__() is not
+current Python, so an implementation of ``dict.__freeze__()`` is not
 provided yet.
 
 .. _1335812: http://sourceforge.net/tracker/index.php?func=detail&aid=1335812&group_id=5470&atid=305470
@@ -155,11 +161,11 @@ Open issues
 - Should dicts and sets automatically freeze their mutable keys?
 
 - Should we support "temporary freezing" (perhaps with a method called
-  __congeal__()) a la __as_temporarily_immutable__() in sets.Set?
+  ``__congeal__()``) a la ``__as_temporarily_immutable__()`` in ``sets.Set``?
 
-- For backward compatibility with sets.Set, should we support
-  __as_immutable__()?  Or should __freeze__() just be renamed to
-  __as_immutable__()?
+- For backward compatibility with ``sets.Set``, should we support
+  ``__as_immutable__()``?  Or should ``__freeze__()`` just be renamed to
+  ``__as_immutable__()``?
 
 
 Copyright

peps/pep-0387.rst

@@ -219,7 +219,7 @@ References
 
 .. [#tiobe] TIOBE Programming Community Index
 
-   http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html
+   https://www.tiobe.com/tiobe-index/
 
 .. [#warnings] The warnings module