-
-
Notifications
You must be signed in to change notification settings - Fork 34.5k
The ABI check has false positives #143253
Copy link
Copy link
Closed
Labels
buildThe build process and cross-buildThe build process and cross-buildinfraCI, GitHub Actions, buildbots, Dependabot, etc.CI, GitHub Actions, buildbots, Dependabot, etc.type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Metadata
Metadata
Assignees
Labels
buildThe build process and cross-buildThe build process and cross-buildinfraCI, GitHub Actions, buildbots, Dependabot, etc.CI, GitHub Actions, buildbots, Dependabot, etc.type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
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