[issue39998] [C API] Remove PyEval_AcquireLock() and PyEval_ReleaseLock() functions

[STINNER Victor]

STINNER Victor <vstinner at python.org> added the comment:

Oh no,  PyEval_AcquireLock() and PyEval_ReleaseLock() are part of the limited C API (and so the stable ABI). Sadly, we have to keep them. I close the issue as rejected.


> We cannot just remove functions from stable ABI.

Alright, sadly it's part of the limited C API :-(

> We can undocument them, remove their declaration from header files, but we can't remove the implementation. Just make them always failing.

Since I found a few projects using these functions, I'm no longer sure that it's worth it to remove these functions.

Continuing to maintain these functions is not really a major maintenance burden right now. So I simply close this issue.

If someone disagree, you can propose an implementation of Serhiy's suggestion.

----------
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue39998>
_______________________________________