> On 14 Feb 2022, at 14:07, Petr Viktorin <encu...@gmail.com> wrote: > > > > On 14. 02. 22 13:37, Antoine Pitrou wrote: >> On Mon, 14 Feb 2022 13:19:00 +0100 >> Petr Viktorin <encu...@gmail.com> 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.
Do you have an example of this? On first glance the pythoncapi_compat.h header only uses public APIs, other than (maybe) accessing fields of the thread state directly. BTW. I’m +1 on providing this header, it makes it easier for projects to maintain compatibility with older Python versions. That said, we should continue to be careful and considerate when evolving the public API as migrating a project to a newer API is still work. Ronald — Twitter / micro.blog: @ronaldoussoren Blog: https://blog.ronaldoussoren.net/
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/B7TKVUPXADTHYANTLIKCAVE4ZCNUJ64M/ Code of Conduct: http://python.org/psf/codeofconduct/
