Clarify API stability of PyTypeObject in relation to static types. (GH-96217)

https://github.com/python/cpython/commit/caa2a9799a47294441e4206037620322eea... commit: caa2a9799a47294441e4206037620322eea9ed06 branch: main author: ov2k <ov2k.github@gmail.com> committer: encukou <encukou@gmail.com> date: 2022-08-25T15:32:12+02: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 files: M Doc/c-api/typeobj.rst diff --git a/Doc/c-api/typeobj.rst b/Doc/c-api/typeobj.rst index b8baa7c7dc3..dfe91ee358d 100644 --- a/Doc/c-api/typeobj.rst +++ b/Doc/c-api/typeobj.rst @@ -2062,9 +2062,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:
participants (1)
-
encukou