mirror of https://github.com/python/cpython
gh-112092: clarify unstable ABI recompilation requirements (#112093)
Use different versions in the examples for when extensions do and do not need to be recompiled to make the examples easier to understand.
This commit is contained in:
parent
7fa511ba57
commit
68a7b78cd5
|
@ -16,7 +16,7 @@ CPython's Application Binary Interface (ABI) is forward- and
|
|||
backwards-compatible across a minor release (if these are compiled the same
|
||||
way; see :ref:`stable-abi-platform` below).
|
||||
So, code compiled for Python 3.10.0 will work on 3.10.8 and vice versa,
|
||||
but will need to be compiled separately for 3.9.x and 3.10.x.
|
||||
but will need to be compiled separately for 3.9.x and 3.11.x.
|
||||
|
||||
There are two tiers of C API with different stability expectations:
|
||||
|
||||
|
|
Loading…
Reference in New Issue