Merge branch 'main' into strftime-runtime-checks

Author: serhiy-storchaka

.github/workflows/mypy.yml

@@ -59,4 +59,5 @@ jobs:
           cache: pip
           cache-dependency-path: Tools/requirements-dev.txt
       - run: pip install -r Tools/requirements-dev.txt
+      - run: python3 Misc/mypy/make_symlinks.py --symlink
       - run: mypy --config-file ${{ matrix.target }}/mypy.ini

Doc/c-api/arg.rst

@@ -113,14 +113,18 @@ There are three ways strings and buffers can be converted to C:
 ``z`` (:class:`str` or ``None``) [const char \*]
    Like ``s``, but the Python object may also be ``None``, in which case the C
    pointer is set to ``NULL``.
+   It is the same as ``s?`` with the C pointer was initialized to ``NULL``.
 
 ``z*`` (:class:`str`, :term:`bytes-like object` or ``None``) [Py_buffer]
    Like ``s*``, but the Python object may also be ``None``, in which case the
    ``buf`` member of the :c:type:`Py_buffer` structure is set to ``NULL``.
+   It is the same as ``s*?`` with the ``buf`` member of the :c:type:`Py_buffer`
+   structure was initialized to ``NULL``.
 
 ``z#`` (:class:`str`, read-only :term:`bytes-like object` or ``None``) [const char \*, :c:type:`Py_ssize_t`]
    Like ``s#``, but the Python object may also be ``None``, in which case the C
    pointer is set to ``NULL``.
+   It is the same as ``s#?`` with the C pointer was initialized to ``NULL``.
 
 ``y`` (read-only :term:`bytes-like object`) [const char \*]
    This format converts a bytes-like object to a C pointer to a
@@ -357,11 +361,37 @@ Other objects
 
    .. versionadded:: 3.3
 
-``(items)`` (:class:`tuple`) [*matching-items*]
-   The object must be a Python sequence whose length is the number of format units
+``(items)`` (sequence) [*matching-items*]
+   The object must be a Python sequence (except :class:`str`, :class:`bytes`
+   or :class:`bytearray`) whose length is the number of format units
    in *items*.  The C arguments must correspond to the individual format units in
    *items*.  Format units for sequences may be nested.
 
+   If *items* contains format units which store a :ref:`borrowed buffer
+   <c-arg-borrowed-buffer>` (``s``, ``s#``, ``z``, ``z#``, ``y``, or ``y#``)
+   or a :term:`borrowed reference` (``S``, ``Y``, ``U``, ``O``, or ``O!``),
+   the object must be a Python tuple.
+   The *converter* for the ``O&`` format unit in *items* must not store
+   a borrowed buffer or a borrowed reference.
+
+   .. versionchanged:: next
+      :class:`str` and :class:`bytearray` objects no longer accepted as a sequence.
+
+   .. deprecated:: next
+      Non-tuple sequences are deprecated if *items* contains format units
+      which store a borrowed buffer or a borrowed reference.
+
+``unit?`` (anything or ``None``) [*matching-variable(s)*]
+   ``?`` modifies the behavior of the preceding format unit.
+   The C variable(s) corresponding to that parameter should be initialized
+   to their default value --- when the argument is ``None``,
+   :c:func:`PyArg_ParseTuple` does not touch the contents of the corresponding
+   C variable(s).
+   If the argument is not ``None``, it is parsed according to the specified
+   format unit.
+
+   .. versionadded:: next
+
 A few other characters have a meaning in a format string.  These may not occur
 inside nested parentheses.  They are:
 

Doc/c-api/buffer.rst

@@ -26,17 +26,19 @@ characteristic of being backed by a possibly large memory buffer.  It is
 then desirable, in some situations, to access that buffer directly and
 without intermediate copying.
 
-Python provides such a facility at the C level in the form of the :ref:`buffer
-protocol <bufferobjects>`.  This protocol has two sides:
+Python provides such a facility at the C and Python level in the form of the
+:ref:`buffer protocol <bufferobjects>`.  This protocol has two sides:
 
 .. index:: single: PyBufferProcs (C type)
 
 - on the producer side, a type can export a "buffer interface" which allows
   objects of that type to expose information about their underlying buffer.
-  This interface is described in the section :ref:`buffer-structs`;
+  This interface is described in the section :ref:`buffer-structs`; for
+  Python see :ref:`python-buffer-protocol`.
 
 - on the consumer side, several means are available to obtain a pointer to
-  the raw underlying data of an object (for example a method parameter).
+  the raw underlying data of an object (for example a method parameter). For
+  Python see :class:`memoryview`.
 
 Simple objects such as :class:`bytes` and :class:`bytearray` expose their
 underlying buffer in byte-oriented form.  Other forms are possible; for example,
@@ -62,6 +64,10 @@ In both cases, :c:func:`PyBuffer_Release` must be called when the buffer
 isn't needed anymore.  Failure to do so could lead to various issues such as
 resource leaks.
 
+.. versionadded:: 3.12
+
+   The buffer protocol is now accessible in Python, see
+   :ref:`python-buffer-protocol` and :class:`memoryview`.
 
 .. _buffer-structure:
 

Doc/c-api/monitoring.rst

@@ -205,6 +205,6 @@ would typically correspond to a python function.
 
    .. versionadded:: 3.13
 
-   .. deprecated:: next
+   .. deprecated:: 3.14
 
       This function is :term:`soft deprecated`.

Doc/library/ctypes.rst

@@ -2632,7 +2632,7 @@ These are the fundamental ctypes data types:
    Represents the C :c:expr:`PyObject *` datatype.  Calling this without an
    argument creates a ``NULL`` :c:expr:`PyObject *` pointer.
 
-   .. versionchanged:: next
+   .. versionchanged:: 3.14
       :class:`!py_object` is now a :term:`generic type`.
 
 The :mod:`!ctypes.wintypes` module provides quite some other Windows specific
@@ -2846,7 +2846,7 @@ fields, or any other data types containing pointer type fields.
    :class:`!CField` objects are created via :attr:`~Structure._fields_`;
    do not instantiate the class directly.
 
-   .. versionadded:: next
+   .. versionadded:: 3.14
 
       Previously, descriptors only had ``offset`` and ``size`` attributes
       and a readable string representation; the :class:`!CField` class was not

Doc/library/fnmatch.rst

@@ -97,7 +97,7 @@ functions: :func:`fnmatch`, :func:`fnmatchcase`, :func:`.filter`.
    It is the same as ``[n for n in names if not fnmatch(n, pat)]``,
    but implemented more efficiently.
 
-   .. versionadded:: next
+   .. versionadded:: 3.14
 
 
 .. function:: translate(pat)

Doc/library/graphlib.rst

@@ -109,7 +109,7 @@
       A :exc:`ValueError` will be raised if the sort has been started by
       :meth:`~.static_order` or :meth:`~.get_ready`.
 
-      .. versionchanged:: next
+      .. versionchanged:: 3.14
 
          ``prepare()`` can now be called more than once as long as the sort has
          not started. Previously this raised :exc:`ValueError`.

Doc/library/http.server.rst

@@ -78,7 +78,7 @@ handler.  Code to create and run the server looks like this::
 
    By default, it is set to ``["http/1.1"]``, meaning the server supports HTTP/1.1.
 
-   .. versionadded:: next
+   .. versionadded:: 3.14
 
 .. class:: ThreadingHTTPSServer(server_address, RequestHandlerClass,\
                                 bind_and_activate=True, *, certfile, keyfile=None,\
@@ -88,7 +88,7 @@ handler.  Code to create and run the server looks like this::
    requests by inheriting from :class:`~socketserver.ThreadingMixIn`. This is
    analogous to :class:`ThreadingHTTPServer` only using :class:`HTTPSServer`.
 
-   .. versionadded:: next
+   .. versionadded:: 3.14
 
 
 The :class:`HTTPServer`, :class:`ThreadingHTTPServer`, :class:`HTTPSServer` and
@@ -588,15 +588,15 @@ The following options are accepted:
 
       python -m http.server --tls-cert fullchain.pem
 
-   .. versionadded:: next
+   .. versionadded:: 3.14
 
 .. option:: --tls-key
 
    Specifies a private key file for HTTPS connections.
 
    This option requires ``--tls-cert`` to be specified.
 
-   .. versionadded:: next
+   .. versionadded:: 3.14
 
 .. option:: --tls-password-file
 
@@ -609,7 +609,7 @@ The following options are accepted:
 
    This option requires `--tls-cert`` to be specified.
 
-   .. versionadded:: next
+   .. versionadded:: 3.14
 
 
 .. _http.server-security:

Doc/library/multiprocessing.rst

@@ -1425,7 +1425,7 @@ object -- see :ref:`multiprocessing-managers`.
 
       Return a boolean indicating whether this object is locked right now.
 
-      .. versionadded:: next
+      .. versionadded:: 3.14
 
 
 .. class:: RLock()
@@ -1492,7 +1492,7 @@ object -- see :ref:`multiprocessing-managers`.
 
       Return a boolean indicating whether this object is locked right now.
 
-      .. versionadded:: next
+      .. versionadded:: 3.14
 
 
 .. class:: Semaphore([value])

Doc/library/pdb.rst

@@ -769,7 +769,7 @@ can be overridden by the local file.
    When using ``pdb.pm()``  or ``Pdb.post_mortem(...)`` with a chained exception
    instead of a traceback, it allows the user to move between the
    chained exceptions using ``exceptions`` command to list exceptions, and
-   ``exception <number>`` to switch to that exception.
+   ``exceptions <number>`` to switch to that exception.
 
 
    Example::