On 2026-01-16 11:07 AM, Gordon Messmer wrote:
a third code path in which they build with the new API and run without the new ABI
Another reason I dislike this idea in principle is that it is extremely difficult to test this third code path in CI.
Generally, you expect CI to test a binary with the library that's present. That means that systems that have the old expat API will build a Python binary that only requires the old ABI, and any tests that run will exercise the old API+old ABI code path. Systems that have the new API will build a binary that requires the new ABI, and any tests that run will exercise the new API+new ABI code path. But testing the new API + old runtime ABI is difficult. The build tests won't exercise that code path. You could hypothetically build functional tests for this, but they're probably going to be a lot less extensive than the test suite that ships in the project.
-- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
