mirror of
https://github.com/python/cpython.git
synced 2025-10-04 14:15:45 +00:00
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 caa2a9799a
)
Co-authored-by: ov2k <ov2k.github@gmail.com>
This commit is contained in:
parent
888054ae8a
commit
3d14b4fecb
1 changed files with 3 additions and 3 deletions
|
@ -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
|
:ref:`sub-interpreters <sub-interpreter-support>`, so they should not
|
||||||
include any subinterpreter-specific state.
|
include any subinterpreter-specific state.
|
||||||
|
|
||||||
Also, since :c:type:`PyTypeObject` is not part of the :ref:`stable ABI <stable>`,
|
Also, since :c:type:`PyTypeObject` is only part of the :ref:`Limited API
|
||||||
any extension modules using static types must be compiled for a specific
|
<stable>` as an opaque struct, any extension modules using static types must be
|
||||||
Python minor version.
|
compiled for a specific Python minor version.
|
||||||
|
|
||||||
|
|
||||||
.. _heap-types:
|
.. _heap-types:
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue