[3.12] gh-112092: clarify unstable ABI recompilation requirements (GH-112093) (#114260)

gh-112092: clarify unstable ABI recompilation requirements (GH-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.
(cherry picked from commit 68a7b78cd5)

Co-authored-by: DerSchinken <53398996+DerSchinken@users.noreply.github.com>
This commit is contained in:
Miss Islington (bot) 2024-01-18 21:28:04 +01:00 committed by GitHub
parent a76d0104d7
commit f9158d63b1
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -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: