[issue28736] multiprocessing.Lock() no longer has .acquire()

Changes by Zachary Ware : -- resolution: -> not a bug stage: -> resolved ___ Python tracker ___

[issue28736] multiprocessing.Lock() no longer has .acquire()

Eric Leadbetter added the comment: It was a typographical error on my part. My mistake. -- status: open -> closed ___ Python tracker ___

[issue28736] multiprocessing.Lock() no longer has .acquire()

R. David Murray added the comment: 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? -- nosy:

[issue28736] multiprocessing.Lock() no longer has .acquire()

New submission from Eric Leadbetter: The documentation on the multiprocessing library in Python 3 uses Lock.acquire()/Lock.release() in the example for primitive synchronization (https://docs.python.org/3/library/multiprocessing.html#synchronization-between-processes). Lock() has been changed