René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Backport of `PyConfig.use_system_logger` has changed ABI in a patch 3.13.1 -\u003e 3.13.2","articleBody":"# Bug report\n\n### Bug description:\n\nIn https://github.com/python/cpython/pull/127592 a new `PyConfig` flag was added for apple platforms to allow use of the system logger.\n\nThis PR looks like it was backported to all branches from 3.9 through to 3.13, and has been released in 3.13.2 ~~and 3.12.9~~. \n\nUnfortunately, this has changed the public ABI (layout of the `PyConfig` struct) on a patch release. This means that binaries using the `PyConfig` API and built using 3.13.1 or 3.13.0 ~~(or 3.12.8)~~ will potentially misbehave if running against a newer interpreter.\n\nI picked this up after getting a PyO3 \"FFI check\" failure on 3.13.2, reporting that our FFI bindings were no longer compatible with CPython.\n\nIn PEP 741 it was previously noted that backporting a flag to break the public ABI was decided against, so I believe this to be a bug.\n\nDo I wait for CPython to revert this? Or do I make PyO3 adjust to the new ABI (and break compatibility with all existing interpreters)?\n\nping @vstinner as I know you have been very active on this API.\n\n### CPython versions tested on:\n\n3.13\n\n### Operating systems tested on:\n\nmacOS\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-131129\n* gh-131172\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/davidhewitt","@type":"Person","name":"davidhewitt"},"datePublished":"2025-03-07T10:08:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":19},"url":"https://github.com/130940/cpython/issues/130940"}