Thanks. I will do it. On Wed, Jul 1, 2020 at 5:50 PM Serhiy Storchaka <storch...@gmail.com> wrote: > > 01.07.20 04:35, Inada Naoki пише: > > Hi, folks. > > > > I found PyEval_AcquireLock and PyEval_ReleaseLock are deprecated since > > Python 3.2. > > But the same time, stable ABI is defined in Python 3.2 too. > > The deprecated APIs are stable ABI too because `ceval.h` is not > > excluded from the stable ABI PEP. > > > > As far as my understanding, we can not remove them until Python 4.0. Am I > > right? > > > > I will add comment like this. > > /* This is a part of stable ABI. Do not remove until Python 4.0 */ > > We can remove them from public headers, but should keep their > implementation and export their names to preserve the binary compatibility. > _______________________________________________ > 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/255WEQX2JTSNJHHZJ7NYGSAS5WPN7NI5/ > Code of Conduct: http://python.org/psf/codeofconduct/
-- Inada Naoki <songofaca...@gmail.com> _______________________________________________ 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/JDSJIRJP3ENTIM6AHWKLH255ZPQL2FB3/ Code of Conduct: http://python.org/psf/codeofconduct/
