PEP 741: Python Configuration C API

[vstinner (Victor Stinner)]

@steve.dower

My initial concern with this proposal is that I don’t believe there’s a real benefit to having initialization in the limited API.

Adding an API to the limited C API was requested by different users:

• FR: Allow private runtime config to enable extending without breaking the `PyConfig` ABI - #9 by ronaldoussoren
• FR: Allow private runtime config to enable extending without breaking the `PyConfig` ABI - #10 by gpshead
• FR: Allow private runtime config to enable extending without breaking the `PyConfig` ABI - #11 by LostTime76
• [C API] PEP 741: No limited C API to customize Python initialization (PyConfig, PEP 587) · Issue #107954 · python/cpython · GitHub

@steve.dower

I want to see a rationale for why we need version-independent embedding before we commit to a version-independent initialization API, regardless of how the API looks. That rationale isn’t in the PEP yet.

Sure, I will try to summarize the rationale for adding such API to the limited C API.