Import CPython 3.15.1+dev stable branch (2026-10-24)

Summary:
Imported python/cpython `3.15.1+dev` from upstream rev [`e561b19`](https://www.github.com/python/cpython/commit/e561b199e8b43d9734df130c0af99752ae4449bb) (committed 2026-10-24 03:33:11+00:00).

# Commit Info

- Base: (`3.15.1+dev`) - [`45f5b00`](https://www.github.com/python/cpython/commit/45f5b00a9a6e9921ef74cd9ef28acb5b86cafa73) (commit date: 2026-10-23 01:33:45+00:00)
- Imported: (`3.15.1+dev`) - [`e561b19`](https://www.github.com/python/cpython/commit/e561b199e8b43d9734df130c0af99752ae4449bb) (commit date: 2026-10-24 03:33:11+00:00)

# Noteworthy file changes

- Low-signal files (13 added) (NEWS.d, docs, .github)

Complete list of added/removed files: https://www.internalfb.com/intern/everpaste/?color=0&handle=GLFWxzLisT4kWIwMAFoRnBSoTLNmbr0LAAAz

Reviewed By: itamaro

Differential Revision: D127315796

fbshipit-source-id: 63db139180a1fb9e215c05146413289eee58910c

Author: generatedunixname1734921407115435

Doc/builtins/functions.rst

@@ -314,6 +314,10 @@ are always available.  They are listed here in alphabetical order.
    consists of a single expression, or ``'single'`` if it consists of a single
    interactive statement (in the latter case, expression statements that
    evaluate to something other than ``None`` will be printed).
+   It can also be ``'func_type'`` if *source* consists of a
+   function type signature, for example ``(int) -> str``; see
+   :func:`ast.parse` for more information. This mode requires passing
+   :data:`ast.PyCF_ONLY_AST` in *flags*.
 
    The optional arguments *flags* and *dont_inherit* control which
    :ref:`compiler options <ast-compiler-flags>` should be activated
@@ -387,6 +391,9 @@ are always available.  They are listed here in alphabetical order.
       ``ast.PyCF_ALLOW_TOP_LEVEL_AWAIT`` can now be passed in flags to enable
       support for top-level ``await``, ``async for``, and ``async with``.
 
+   .. versionchanged:: 3.8
+      Added support for ``mode='func_type'``.
+
    .. versionchanged:: 3.12
       :exc:`SyntaxError` is raised instead of :exc:`ValueError` when null bytes
       are encountered in *source*.

Doc/c-api/code.rst

@@ -94,11 +94,12 @@ bound into a function.
 
 .. c:function:: int PyCode_Addr2Line(PyCodeObject *co, int byte_offset)
 
-    Return the line number of the instruction that occurs on or before ``byte_offset`` and ends after it.
-    If you just need the line number of a frame, use :c:func:`PyFrame_GetLineNumber` instead.
+    Return the line number of the instruction that occurs on or before
+    ``byte_offset`` and ends after it.  This may be ``O(N)`` in the number of
+    instructions in the code object, so it is not performant for iterating over
+    all the line numbers in a code object.
 
-    For efficiently iterating over the line numbers in a code object, use :pep:`the API described in PEP 626
-    <0626#out-of-process-debuggers-and-profilers>`.
+    If you just need the line number of a frame, use :c:func:`PyFrame_GetLineNumber` instead.
 
 .. c:function:: int PyCode_Addr2Location(PyObject *co, int byte_offset, int *start_line, int *start_column, int *end_line, int *end_column)