https://github.com/python/cpython/commit/3d14b4fecb859c31123ffc07f278e9cce6b... commit: 3d14b4fecb859c31123ffc07f278e9cce6b80e2d branch: 3.11 author: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> committer: miss-islington <31488909+miss-islington@users.noreply.github.com> date: 2022-08-25T06:42:14-07:00 summary: Clarify API stability of PyTypeObject in relation to static types. (GH-96217) Fixes: https://github.com/python/cpython/issues/95300 Related: https://github.com/python/cpython/issues/91271 (cherry picked from commit caa2a9799a47294441e4206037620322eea9ed06) Co-authored-by: ov2k <ov2k.github@gmail.com> files: M Doc/c-api/typeobj.rst diff --git a/Doc/c-api/typeobj.rst b/Doc/c-api/typeobj.rst index 47e1c8602197..01d67a5a498f 100644 --- a/Doc/c-api/typeobj.rst +++ b/Doc/c-api/typeobj.rst @@ -2041,9 +2041,9 @@ This results in types that are limited relative to types defined in Python: :ref:`sub-interpreters <sub-interpreter-support>`, so they should not include any subinterpreter-specific state. -Also, since :c:type:`PyTypeObject` is not part of the :ref:`stable ABI <stable>`, -any extension modules using static types must be compiled for a specific -Python minor version. +Also, since :c:type:`PyTypeObject` is only part of the :ref:`Limited API +<stable>` as an opaque struct, any extension modules using static types must be +compiled for a specific Python minor version. .. _heap-types: