From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Thu, 25 Aug 2022 13:42:32 +0000 (-0700) Subject: Clarify API stability of PyTypeObject in relation to static types. (GH-96217) X-Git-Tag: v3.10.7~36 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2f88289cf59d7f0941534e40bdd41a5f26f1c605;p=thirdparty%2FPython%2Fcpython.git 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 --- diff --git a/Doc/c-api/typeobj.rst b/Doc/c-api/typeobj.rst index 8d7a2ed75fc9..9bb0e6dbbcf8 100644 --- a/Doc/c-api/typeobj.rst +++ b/Doc/c-api/typeobj.rst @@ -2047,9 +2047,9 @@ This results in types that are limited relative to types defined in Python: :ref:`sub-interpreters `, so they should not include any subinterpreter-specific state. -Also, since :c:type:`PyTypeObject` is not part of the :ref:`stable ABI `, -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 +` as an opaque struct, any extension modules using static types must be +compiled for a specific Python minor version. .. _heap-types: