Issue 10913: Deprecate PyEval_AcquireLock() and PyEval_ReleaseLock() (original) (raw)

Issue10913

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:11 admin set github: 55122
2011-01-15 13:23:41 pitrou set status: open -> closedmessages: + resolution: fixedstage: resolved
2011-01-15 11:22:12 pitrou create