[New-bugs-announce] [issue39998] [C API] Remove PyEval_AcquireLock() and PyEval_ReleaseLock() functions

[STINNER Victor]

New submission from STINNER Victor <vstinner at python.org>:

The PyEval_AcquireLock() and PyEval_ReleaseLock() functions are misleading and deprecated since Python 3.2.

bpo-10913 deprecated them:

commit 5ace8e98da6401827f607292a066da05df3ec5c1
Author: Antoine Pitrou <solipsis at pitrou.net>
Date:   Sat Jan 15 13:11:48 2011 +0000

    Issue #10913: Deprecate misleading functions PyEval_AcquireLock() and
    PyEval_ReleaseLock().  The thread-state aware APIs should be used instead.

It's now time to remove them!

I *discovered* these functions while working on bpo-39984. Previously, I never ever used them nor really see them. I only made refactoring them in their code, without paying attention to them.

----------
components: C API
messages: 364487
nosy: vstinner
priority: normal
severity: normal
status: open
title: [C API] Remove PyEval_AcquireLock() and PyEval_ReleaseLock() functions
versions: Python 3.9

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