gh-108525: Clarify stable ABI documentation to exclude internal C libraries #108582
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #108525
Please see issue #108525 for background. I could not find any information in the documentation on if ABI compatibility between bugfix release shared objects is a warranty. However, using the private API in the C support libraries like _ssl appears to be common and would cause ABI breakage on private API changes.
If this interpretation is incorrect, please let me know as I think clarification would be helpful regardless.
馃摎 Documentation preview 馃摎: https://cpython-previews--108582.org.readthedocs.build/