The check-abidump target reports ABI changes for types defined in Include/internal/pycore_*.h headers, even though these are explicitly not part of CPython's public ABI. For example, adding a field to _ceval_runtime_state or modifying `_PyRuntimeState`` triggers ABI violation warnings.
This happens because internal types are transitively reachable through public API functions like PyInterpreterState_Clear(), causing libabigail to report changes even with --drop-private-types.
Linked PRs
The
check-abidumptarget reports ABI changes for types defined inInclude/internal/pycore_*.hheaders, even though these are explicitly not part of CPython's public ABI. For example, adding a field to_ceval_runtime_stateor modifying `_PyRuntimeState`` triggers ABI violation warnings.This happens because internal types are transitively reachable through public API functions like
PyInterpreterState_Clear(), causing libabigail to report changes even with --drop-private-types.Linked PRs