Skip to content

Commit 3d14b4f

Browse files
miss-islingtonov2k
andauthored
Clarify API stability of PyTypeObject in relation to static types. (GH-96217)
Fixes: #95300 Related: #91271 (cherry picked from commit caa2a97) Co-authored-by: ov2k <[email protected]>
1 parent 888054a commit 3d14b4f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Doc/c-api/typeobj.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2041,9 +2041,9 @@ This results in types that are limited relative to types defined in Python:
20412041
:ref:`sub-interpreters <sub-interpreter-support>`, so they should not
20422042
include any subinterpreter-specific state.
20432043

2044-
Also, since :c:type:`PyTypeObject` is not part of the :ref:`stable ABI <stable>`,
2045-
any extension modules using static types must be compiled for a specific
2046-
Python minor version.
2044+
Also, since :c:type:`PyTypeObject` is only part of the :ref:`Limited API
2045+
<stable>` as an opaque struct, any extension modules using static types must be
2046+
compiled for a specific Python minor version.
20472047

20482048

20492049
.. _heap-types:

0 commit comments

Comments
 (0)