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.

Title: multiprocessing.Lock() no longer has .acquire()
Type: Stage: resolved
Components: Documentation Versions: Python 3.7, Python 3.6, Python 3.3, Python 3.4, Python 3.5
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Eric Leadbetter, docs@python, r.david.murray
Priority: normal Keywords:

Created on 2016-11-18 16:32 by Eric Leadbetter, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (3)
msg281141 - (view) Author: Eric Leadbetter (Eric Leadbetter) Date: 2016-11-18 16:32
The documentation on the multiprocessing library in Python 3 uses Lock.acquire()/Lock.release() in the example for primitive synchronization ( Lock() has been changed in Python 3 to use coroutines and so the documentation should replace the call to Lock.acquire() with an appropriate yield statement.
msg281152 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2016-11-18 17:45
What gives you the idea that the multiprocessing Lock implementation has been changed?  Are you confusing the asyncio Lock with the threading Lock?  Is there a documentation crosslink somewhere that is going to the wrong place?
msg281157 - (view) Author: Eric Leadbetter (Eric Leadbetter) Date: 2016-11-18 18:45
It was a typographical error on my part. My mistake.
Date User Action Args
2022-04-11 14:58:39adminsetgithub: 72922
2016-11-18 19:03:42zach.waresetresolution: not a bug
stage: resolved
2016-11-18 18:45:18Eric Leadbettersetstatus: open -> closed

messages: + msg281157
2016-11-18 17:45:26r.david.murraysetnosy: + r.david.murray
messages: + msg281152
2016-11-18 16:32:34Eric Leadbettercreate