Add PyABIInfo_Check to the c-api - #8941

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

Walkthrough

The change moves PyABIInfo to modsupport, adds ABI support validation, and exposes that validation through PyABIInfo_Check. The check accepts ABI major version 0 and validates version 1 flags.

Changes

PyABIInfo validation

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Security Blast Radius

• inferred — The demonstrated exposure is an in-process native C API within an attached interpreter. The inspected path does not establish a Python-level attacker entrypoint or expanded privilege; external native callers and their exposure remain unknown.

Trust Boundaries and Controls

• observed — The checker relies on native caller obligations: the descriptor must remain valid and immutable during its borrow, and a non-null module name must reference a valid C string. VM attachment is required by the existing helper. The function does not acquire capabilities, transfer ownership or attach a VM itself.

Resilience and Maintainability Implications

• observed — Failures replace the current interpreter exception and return -1; success returns 0 without clearing an existing exception. Repeated calls therefore inherit the established C API error-state behavior. The check creates no reservation, retained resource or ownership transition requiring rollback or cleanup.

❌ Failed checks (1 warning)

• X
• Mastodon
• Reddit
• LinkedIn