Merge remote-tracking branch 'upstream/main' into clinic-s-z-asutf8nonul

# Conflicts:
#	Modules/_ctypes/clinic/_ctypes.c.h
#	Modules/_io/clinic/fileio.c.h
#	Modules/_io/clinic/textio.c.h
#	Modules/_io/clinic/winconsoleio.c.h
#	Modules/_sqlite/clinic/connection.c.h
#	Modules/cjkcodecs/clinic/multibytecodec.c.h
#	Modules/clinic/_dbmmodule.c.h
#	Modules/clinic/_elementtree.c.h
#	Modules/clinic/_gdbmmodule.c.h
#	Modules/clinic/_pickle.c.h
#	Modules/clinic/_testclinic.c.h
#	Modules/clinic/_tkinter.c.h
#	Modules/clinic/arraymodule.c.h
#	Modules/clinic/posixmodule.c.h
#	Modules/clinic/pyexpat.c.h
#	Objects/clinic/memoryobject.c.h
#	Python/clinic/bltinmodule.c.h
#	Python/clinic/sysmodule.c.h

Author: cmaloney

Doc/conf.py

@@ -469,6 +469,10 @@
 # https://github.com/sphinx-doc/sphinx/issues/12359
 epub_use_index = False
 
+# The default depth of 3 lists over a thousand entries, which makes the
+# table of contents hard to navigate in e-book readers
+epub_tocdepth = 2
+
 # translation tag
 # ---------------
 

Doc/library/dis.rst

@@ -1899,32 +1899,38 @@ iterations of the loop.
 
    The operand determines which intrinsic function is called:
 
-   +------------------------------------------+-----------------------------------+
-   | Operand                                  | Description                       |
-   +==========================================+===================================+
-   | ``INTRINSIC_2_INVALID``                  | Not valid                         |
-   +------------------------------------------+-----------------------------------+
-   | ``INTRINSIC_PREP_RERAISE_STAR``          | Calculates the                    |
-   |                                          | :exc:`ExceptionGroup` to raise    |
-   |                                          | from a ``try-except*``.           |
-   +------------------------------------------+-----------------------------------+
-   | ``INTRINSIC_TYPEVAR_WITH_BOUND``         | Creates a :class:`typing.TypeVar` |
-   |                                          | with a bound.                     |
-   +------------------------------------------+-----------------------------------+
-   | ``INTRINSIC_TYPEVAR_WITH_CONSTRAINTS``   | Creates a                         |
-   |                                          | :class:`typing.TypeVar` with      |
-   |                                          | constraints.                      |
-   +------------------------------------------+-----------------------------------+
-   | ``INTRINSIC_SET_FUNCTION_TYPE_PARAMS``   | Sets the ``__type_params__``      |
-   |                                          | attribute of a function.          |
-   +------------------------------------------+-----------------------------------+
-   | ``INTRINSIC_ADD_CONDITIONAL_ANNOTATION`` | Adds an annotation index to the   |
-   |                                          | ``__conditional_annotations__``   |
-   |                                          | set.                              |
-   +------------------------------------------+-----------------------------------+
+   +------------------------------------------+-----------------------------------------+
+   | Operand                                  | Description                             |
+   +==========================================+=========================================+
+   | ``INTRINSIC_2_INVALID``                  | Not valid                               |
+   +------------------------------------------+-----------------------------------------+
+   | ``INTRINSIC_PREP_RERAISE_STAR``          | Calculates the                          |
+   |                                          | :exc:`ExceptionGroup` to raise          |
+   |                                          | from a ``try-except*``.                 |
+   +------------------------------------------+-----------------------------------------+
+   | ``INTRINSIC_TYPEVAR_WITH_BOUND``         | Creates a :class:`typing.TypeVar`       |
+   |                                          | with a bound.                           |
+   +------------------------------------------+-----------------------------------------+
+   | ``INTRINSIC_TYPEVAR_WITH_CONSTRAINTS``   | Creates a                               |
+   |                                          | :class:`typing.TypeVar` with            |
+   |                                          | constraints.                            |
+   +------------------------------------------+-----------------------------------------+
+   | ``INTRINSIC_SET_FUNCTION_TYPE_PARAMS``   | Sets the ``__type_params__``            |
+   |                                          | attribute of a function.                |
+   +------------------------------------------+-----------------------------------------+
+   | ``INTRINSIC_ADD_CONDITIONAL_ANNOTATION`` | Adds an annotation index to the         |
+   |                                          | ``__conditional_annotations__``         |
+   |                                          | set.                                    |
+   +------------------------------------------+-----------------------------------------+
+   | ``INTRINSIC_MATCH_CLASS_ISINSTANCE``     | Do :func:`isinstance` checks for        |
+   |                                          | :ref:`Class patterns <class-patterns>`. |
+   +------------------------------------------+-----------------------------------------+
 
    .. versionadded:: 3.12
 
+   .. versionchanged:: 3.16
+      Added ``INTRINSIC_MATCH_CLASS_ISINSTANCE``.
+
 
 .. opcode:: LOAD_SPECIAL
 

Doc/library/optparse.rst

@@ -16,15 +16,12 @@ Choosing an argument parsing library
 The standard library includes three argument parsing libraries:
 
 * :mod:`getopt`: a module that closely mirrors the procedural C ``getopt`` API.
-  Included in the standard library since before the initial Python 1.0 release.
 * :mod:`!optparse`: a declarative replacement for ``getopt`` that
   provides equivalent functionality without requiring each application
-  to implement its own procedural option parsing logic. Included
-  in the standard library since the Python 2.3 release.
+  to implement its own procedural option parsing logic.
 * :mod:`argparse`: a more opinionated alternative to ``optparse`` that
   provides more functionality by default, at the expense of reduced application
-  flexibility in controlling exactly how arguments are processed. Included in
-  the standard library since the Python 2.7 and Python 3.2 releases.
+  flexibility in controlling exactly how arguments are processed.
 
 In the absence of more specific argument parsing design constraints, :mod:`argparse`
 is the recommended choice for implementing command line applications, as it offers

Doc/library/turtle.rst

@@ -2689,12 +2689,51 @@ These modified docstrings are created automatically together with the function
 definitions that are derived from the methods at import time.
 
 
+.. _turtle-docstring-translation:
+
 Translation of docstrings into different languages
 --------------------------------------------------
 
-There is a utility to create a dictionary the keys of which are the method names
-and the values of which are the docstrings of the public methods of the classes
-Screen and Turtle.
+The docstrings of the public methods of the Screen and Turtle classes, and of
+the corresponding functions, can be replaced with translations, so that
+:func:`help` and IDE tooltips are shown in another language. However, only the help
+text is translated, the names of the functions and methods stay the same.
+
+Translations are distributed on PyPI in the :pypi:`turtle-translations`
+package. To use them, install the package with :program:`pip` and select the
+language with the :envvar:`PYTHON_TURTLE_LANG` environment variable. For
+example, to show the help text in Spanish:
+
+.. code-block:: console
+
+   $ python -m pip install turtle-translations
+   $ PYTHON_TURTLE_LANG=es python
+   >>> import turtle
+   >>> help(turtle.forward)
+
+The language can also be set permanently with the *language* entry of the
+:file:`turtle.cfg` file (see :ref:`turtle-configuration`). If no translation
+is found for the selected language, the English docstrings are kept.
+
+To add a new language or improve an existing translation, see the
+contribution instructions in the :pypi:`turtle-translations` project.
+
+A translation is a docstring dictionary. It is a top-level module named
+:samp:`turtle_docstringdict_{language}.py` on :data:`sys.path` defining a
+dictionary named ``docsdict``, the keys of which are method names such as
+``Turtle.forward`` and the values of which are the translated docstrings. It is
+read in at import time. Entries naming a method which does not exist in the
+running version are ignored.
+
+.. versionchanged:: 3.16
+   Entries naming an unknown method are ignored instead of reported.
+
+.. envvar:: PYTHON_TURTLE_LANG
+
+   The name of the language to read the translation for. It takes precedence
+   over the *language* entry of the :file:`turtle.cfg` file.
+
+   .. versionadded:: 3.16
 
 .. function:: write_docstringdict(filename="turtle_docstringdict")
 
@@ -2706,17 +2745,8 @@ Screen and Turtle.
    Python script :file:`{filename}.py`.  It is intended to serve as a template
    for translation of the docstrings into different languages.
 
-If you (or your students) want to use :mod:`!turtle` with online help in your
-native language, you have to translate the docstrings and save the resulting
-file as e.g. :file:`turtle_docstringdict_german.py`.
-
-If you have an appropriate entry in your :file:`turtle.cfg` file this dictionary
-will be read in at import time and will replace the original English docstrings.
-
-At the time of this writing there are docstring dictionaries in German and in
-Italian.  (Requests please to glingl@aon.at.)
-
 
+.. _turtle-configuration:
 
 How to configure Screen and Turtles
 -----------------------------------
@@ -2767,9 +2797,9 @@ Short explanation of selected entries:
   the cfg file).
 - If you want to reflect the turtle its state, you have to use ``resizemode =
   auto``.
-- If you set e.g. ``language = italian`` the docstringdict
-  :file:`turtle_docstringdict_italian.py` will be loaded at import time (if
-  present on the import path, e.g. in the same directory as :mod:`!turtle`).
+- The *language* entry selects the language of the docstrings, unless the
+  :envvar:`PYTHON_TURTLE_LANG` environment variable is set. See
+  :ref:`turtle-docstring-translation` for more information.
 - The entries *exampleturtle* and *examplescreen* define the names of these
   objects as they occur in the docstrings.  The transformation of
   method-docstrings to function-docstrings will delete these names from the

Doc/whatsnew/3.15.rst

@@ -2030,21 +2030,18 @@ Upgraded experimental JIT compiler
 ----------------------------------
 
 Results from the `pyperformance <https://github.com/python/pyperformance>`__
-benchmark suite report
-`8-9% <https://www.doesjitgobrrr.com/run/2026-04-29>`__
+benchmark suite report a
+`7-8% <https://www.doesjitgobrrr.com/run/2026-09-25>`__
 geometric mean performance improvement for the JIT over the standard CPython
 interpreter built with all optimizations enabled on x86-64 Linux. On AArch64
-macOS, the JIT has a
-`12-13% <https://www.doesjitgobrrr.com/run/2026-04-29>`__
+macOS, the JIT has an
+`11-12% <https://www.doesjitgobrrr.com/run/2026-09-25>`__
 speedup over the :ref:`tail calling interpreter <whatsnew314-tail-call-interpreter>`
 with all optimizations enabled. The speedups for JIT
 builds versus no JIT builds range from roughly 15% slowdown to over
 100% speedup (ignoring the ``unpack_sequence`` microbenchmark) on
 x86-64 Linux and AArch64 macOS systems.
 
-.. attention::
-    These results are not yet final.
-
 The major upgrades to the JIT are:
 
 * LLVM 21 build-time dependency

Doc/whatsnew/3.16.rst

@@ -712,6 +712,16 @@ tkinter
   with no unit suffix to :class:`int` or :class:`float`.
   (Contributed by Serhiy Storchaka in :gh:`153513`.)
 
+
+turtle
+------
+
+* Translations of the :mod:`turtle` docstrings are now distributed on PyPI
+  in the :pypi:`turtle-translations` package. Additionally, added the
+  :envvar:`PYTHON_TURTLE_LANG` environment variable to select the language.
+  (Contributed by Stan Ulbrych in :gh:`156360`.)
+
+
 unicodedata
 -----------
 

Include/internal/pycore_global_objects_fini_generated.h

@@ -500,7 +500,9 @@ struct _Py_global_strings {
         STRUCT_FOR_ID(filter)
         STRUCT_FOR_ID(filters)
         STRUCT_FOR_ID(final)
+        STRUCT_FOR_ID(finalizer)
         STRUCT_FOR_ID(find_class)
+        STRUCT_FOR_ID(firstiter)
         STRUCT_FOR_ID(fix_imports)
         STRUCT_FOR_ID(flags)
         STRUCT_FOR_ID(flush)

Include/internal/pycore_global_strings.h

@@ -31,8 +31,9 @@
 #define INTRINSIC_SET_FUNCTION_TYPE_PARAMS       4
 #define INTRINSIC_SET_TYPEPARAM_DEFAULT          5
 #define INTRINSIC_ADD_CONDITIONAL_ANNOTATION     6
+#define INTRINSIC_MATCH_CLASS_ISINSTANCE         7
 
-#define MAX_INTRINSIC_2                          6
+#define MAX_INTRINSIC_2                          7
 
 typedef PyObject *(*intrinsic_func1)(PyThreadState* tstate, PyObject *value);
 typedef PyObject *(*intrinsic_func2)(PyThreadState* tstate, PyObject *value1, PyObject *value2);

Include/internal/pycore_intrinsics.h

@@ -303,6 +303,7 @@ Known values:
     Python 3.16a1 3703 (Replace DELETE_GLOBAL with PUSH_NULL; STORE_GLOBAL)
     Python 3.16a1 3704 (Replace DELETE_ATTR with PUSH_NULL; STORE_ATTR)
     Python 3.16a1 3705 (Add INTRINSIC_ADD_CONDITIONAL_ANNOTATION)
+    Python 3.16a1 3706 (Add INTRINSIC_MATCH_CLASS_ISINSTANCE)
 
     Python 3.17 will start with 3750
 
@@ -312,7 +313,7 @@ Known values:
 
 */
 
-#define PYC_MAGIC_NUMBER 3705
+#define PYC_MAGIC_NUMBER 3706
 /* This is equivalent to converting PYC_MAGIC_NUMBER to 2 bytes
    (little-endian) and then appending b'\r\n'. */
 #define PYC_MAGIC_NUMBER_TOKEN \