Repository navigation
Deprecate PyEval_AcquireLock() and PyEval_ReleaseLock() #55122
Description
| BPO | 10913 |
|---|---|
| Nosy | @pitrou |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = 'https://github.com/pitrou'
closed_at = <Date 2011-01-15.13:23:41.360>
created_at = <Date 2011-01-15.11:22:12.010>
labels = ['type-bug', 'docs']
title = 'Deprecate PyEval_AcquireLock() and PyEval_ReleaseLock()'
updated_at = <Date 2011-01-15.13:23:41.359>
user = 'https://github.com/pitrou'bugs.python.org fields:
activity = <Date 2011-01-15.13:23:41.359>
actor = 'pitrou'
assignee = 'pitrou'
closed = True
closed_date = <Date 2011-01-15.13:23:41.360>
closer = 'pitrou'
components = ['Documentation']
creation = <Date 2011-01-15.11:22:12.010>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 10913
keywords = []
message_count = 2.0
messages = ['126324', '126327']
nosy_count = 2.0
nosy_names = ['pitrou', 'grahamd']
pr_nums = []
priority = 'high'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue10913'
versions = ['Python 3.2']
Activity
pitrou commentedon Jan 15, 2011
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 bpo-1720250 for an example confusion.
pitrou commentedon Jan 15, 2011
Done in r88018.