Merge branch 'main' into relative.venvs

Author: AA-Turner

.github/CODEOWNERS

@@ -679,6 +679,10 @@ peps/pep-0799.rst  @pablogsal
 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-2026.rst  @hugovk
 # ...

.github/workflows/lint.yml

@@ -19,7 +19,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
         with:
           persist-credentials: false
 

.github/workflows/render.yml

@@ -27,7 +27,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           fetch-depth: 0  # fetch all history so that last modified date-times are accurate
 

.github/workflows/test.yml

@@ -30,7 +30,6 @@ jobs:
       fail-fast: false
       matrix:
         python-version:
-        - "3.9"
         - "3.10"
         - "3.11"
         - "3.12"
@@ -42,7 +41,7 @@ jobs:
         - "ubuntu-latest"
 
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
         with:
           persist-credentials: false
 

.ruff.toml

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

pep_sphinx_extensions/pep_theme/templates/page.html

@@ -55,7 +55,7 @@ <h2>Contents</h2>
             {{ toc }}
             <br>
             {%- if not pagename.startswith(("pep-0000", "topic")) %}
-            <a id="source" href="https://github.com/python/peps/blob/main/peps/{{pagename}}.rst">Page Source (GitHub)</a>
+            <a id="source" href="https://github.com/python/peps/blob/main/peps/{{pagename}}.rst?plain=1">Page Source (GitHub)</a>
             {%- endif %}
         </nav>
         {%- endif %}

peps/pep-0007.rst

@@ -26,12 +26,24 @@ particular rule:
    clean up someone else's mess (in true XP style).
 
 
-C dialect
-=========
+.. _c_dialect:
+
+C standards
+===========
+
+Follow the following standards.
+For features that aren't in the relevant standard, use CPython-specific
+wrappers (for example: ``_Py_atomic_store_int32``, ``Py_ALWAYS_INLINE``,
+``Py_ARITHMETIC_RIGHT_SHIFT``; ``_Py_ALIGNED_DEF`` in public headers).
+When adding such wrappers, try to make them easy to adjust for unsupported
+compilers.
 
 * Python 3.11 and newer versions use C11 without `optional features
-  <https://en.wikipedia.org/wiki/C11_%28C_standard_revision%29#Optional_features>`_.
-  The public C API should be compatible with C++.
+  <https://en.wikipedia.org/wiki/C11_%28C_standard_revision%29#Optional_features>`__.
+  The public C API should be compatible with C99 and C++.
+
+  (As a reminder to any users reading this: this PEP is a *style guide*; these
+  rules are there to be broken.)
 
 * Python 3.6 to 3.10 use C89 with several select C99 features:
 
@@ -44,15 +56,19 @@ C dialect
   - C++-style line comments
 
 * Python versions before 3.6 used ANSI/ISO standard C (the 1989 version
-  of the standard).  This meant (amongst many other things) that all
-  declarations must be at the top of a block (not necessarily at the
-  top of function).
+  of the standard).  This meant, amongst many other things, that all
+  declarations were at the top of a block.
+
+
+Common C code conventions
+=========================
 
-* Don't use compiler-specific extensions, such as those of GCC or MSVC
-  (e.g. don't write multi-line strings without trailing backslashes).
+* Don't use compiler-specific extensions, such as those of GCC or MSVC.
+  For example, don't write multi-line strings without trailing backslashes.
 
-* All function declarations and definitions must use full prototypes
-  (i.e. specify the types of all arguments).
+* All function declarations and definitions must use full prototypes.
+  That is, specify the types of all arguments and use ``(void)`` to declare
+  functions with no arguments.
 
 * No compiler warnings with major compilers (gcc, VC++, a few others).
 

peps/pep-0011.rst

@@ -83,7 +83,6 @@ aarch64-apple-darwin      clang
 aarch64-unknown-linux-gnu glibc, gcc
 i686-pc-windows-msvc
 x86_64-pc-windows-msvc
-x86_64-apple-darwin       BSD libc, clang
 x86_64-unknown-linux-gnu  glibc, gcc
 ========================= =====
 
@@ -103,6 +102,7 @@ Target Triple                 Notes                      Contacts
 ============================= ========================== ========
 aarch64-unknown-linux-gnu     glibc, clang               Victor Stinner, Gregory P. Smith
 wasm32-unknown-wasip1         WASI SDK, Wasmtime         Brett Cannon, Michael Droettboom
+x86_64-apple-darwin           macOS, clang               Sam Gross, Barry Warsaw, Ronald Oussoren
 x86_64-unknown-linux-gnu      glibc, clang               Victor Stinner, Gregory P. Smith
 ============================= ========================== ========
 
@@ -123,7 +123,7 @@ aarch64-linux-android                                        Russell Keith-Magee
 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   Raspberry Pi OS, glibc, gcc Gregory P. Smith
+armv7l-unknown-linux-gnueabihf   32-bit Raspberry Pi OS, gcc Gregory P. Smith
 powerpc64le-unknown-linux-gnu    glibc, clang                Victor Stinner
 
                                  glibc, gcc                  Victor Stinner

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