This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Deprecate PyEval_AcquireLock() and PyEval_ReleaseLock()
Type: behavior Stage: resolved
Components: Documentation Versions: Python 3.2
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: pitrou Nosy List: grahamd, pitrou
Priority: high Keywords:

Created on 2011-01-15 11:22 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg126324 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2011-01-15 11:22
These two functions are very low-level and no good to use outside the interpreter core (actually, inside the core I don't think they are useful either). We should deprecate them and recommend the thread-state aware functions instead. See #1720250 for an example confusion.
msg126327 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2011-01-15 13:23
Done in r88018.
History
Date User Action Args
2022-04-11 14:57:11adminsetgithub: 55122
2011-01-15 13:23:41pitrousetstatus: open -> closed

messages: + msg126327
resolution: fixed
stage: resolved
2011-01-15 11:22:12pitroucreate