PyEval_ReleaseLock() is deprecated since Python 3.2 in the documentation: https://docs.python.org/dev/c-api/init.html#c.PyEval_ReleaseLock
PyEval_AcquireLock() was annotated with Py_DEPRECATED() by Serhiy Storchaka in https://bugs.python.org/issue19569#msg280110 where he wrote: "PyEval_ReleaseLock() is used in Python/pystate.c. It can't be replaced with PyEval_ReleaseThread() since the latter don't accept NULL." I wrote in a previous email, I modified Python internals to no longer call PyEval_ReleaseLock(), but a new internal _PyEval_ReleaseLock(tstate) function instead. Maybe we can still mark PyEval_ReleaseLock() as deprecated in Python 3.9, since it's just compiler warning, it's less intrusive than a warning emitted at runtime. Victor Le ven. 3 juil. 2020 à 11:28, Inada Naoki <songofaca...@gmail.com> a écrit : > > On Fri, Jul 3, 2020 at 6:23 PM Victor Stinner <vstin...@python.org> wrote: > > > > > > So it seems possible to fix JEP and pydevd-pycharm. IMHO it's fine to > > remove PyEval_ReleaseLock() in Python 3.10. The deprecation warning is > > there since Python 3.2. > > > > While PyEval_AcquireLock is deprecated, PyEval_ReleaseLock is not > deprecated yet in C. > https://github.com/python/cpython/blob/master/Include/ceval.h#L132 > > Maybe, we can uncomment Py_DEPRECATE in 3.10, and remove it from > header file in 3.12. > > Regards, > -- > Inada Naoki <songofaca...@gmail.com> -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ 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/OSGWHNO2N2E4YN7JJDZ3YA5VUVKB6MIE/ Code of Conduct: http://python.org/psf/codeofconduct/
