intersphinx

Author: JelleZijlstra

peps/conf.py

@@ -73,6 +73,7 @@
     "py3.12": ("https://docs.python.org/3.12/", None),
     "py3.13": ("https://docs.python.org/3.13/", None),
     "py3.14": ("https://docs.python.org/3.14/", None),
+    "py3.15": ("https://docs.python.org/3.15/", None),
     "python": ("https://docs.python.org/3/", None),
     "trio": ("https://trio.readthedocs.io/en/latest/", None),
     "typing": ("https://typing.python.org/en/latest/", None),

peps/pep-0800.rst

@@ -176,8 +176,8 @@ and are described below.)
 Runtime restrictions on multiple inheritance
 --------------------------------------------
 
-While Python generally allows multiple inheritance, the runtime imposes various restrictions, as documented in
-`CPython <https://docs.python.org/3.15/reference/compound_stmts.html#multiple-inheritance>`__.
+While Python generally allows multiple inheritance, the runtime imposes various restrictions, as
+:external+py3.15:ref:`documented in CPython <multiple-inheritance>`.
 Two sets of restrictions, around a consistent MRO and a consistent metaclass, can already be implemented by
 type checkers using information available in the type system. The third restriction, around instance layout,
 is the one that requires knowledge of disjoint bases. Classes that contain a non-empty ``__slots__`` definition