Skip to content

gh-108525: Clarify stable ABI documentation to exclude internal C libraries #108582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

gh-108525: Clarify stable ABI documentation to exclude internal C libraries #108582

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions Doc/c-api/stable.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,12 @@ 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.

ABI compatibility only applies to public API usage (names not prefixed by an
underscore). Python internal shared libraries (such as the _ssl module) may
utilize the private API and are not guaranteed to be ABI compatible.
For example, the internal _ssl shared library compiled from Python 3.11.5 cannot
be used with a Python 3.11.4 executable.

There are two tiers of C API with different stability exepectations:

- :ref:`Unstable API <unstable-c-api>`, may change in minor versions without
Expand Down