On 14. 02. 22 13:37, Antoine Pitrou wrote:
On Mon, 14 Feb 2022 13:19:00 +0100
Petr Viktorin <[email protected]> wrote:
If we don't have much sympathy for projects that use private API where
does that leave pythoncapi_compat?
If you look at pythoncapi_compat.h, it provides backports for
recently-introduced public APIs such as PyObject_CallOneArg().
Yes.
On older Python versions, where the public API wasn't yet available,
those backports use private API. If we change the private API in a point
release, the backport will break.
Is this a proposal for "blessing" these specific workarounds, and making
sure they don't break? That sounds nice, actually. It would mean some
additional work, though.
_______________________________________________
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/2C3XNK4WDBQISOOHBOYJ5GGZHNY64F77/
Code of Conduct: http://python.org/psf/codeofconduct/
