[issue10789] Lock.acquire documentation is misleading
New submission from Jyrki Pulliainen
Terry J. Reedy
from threading import Lock l=Lock() l.acquire(blocking=True) Traceback (most recent call last): File "
", line 1, in <module> l.acquire(blocking=True) TypeError: acquire() takes no keyword arguments l.acquire(True) True
r87596, r87596 In 3.2: lock.acquire(waitflag=1, timeout=-1) Lock.acquire(blocking=True, timeout=-1) The edit in 3.2 is actually correct
from threading import Lock l=Lock() l.acquire(blocking=True) True l.acquire(timeout=1) False
_thread.lock.acquire now accepts keywords.
----------
assignee: docs@python -> terry.reedy
nosy: +terry.reedy
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
_______________________________________
Python tracker
Éric Araujo
Georg Brandl
Terry J. Reedy
Éric Araujo
Raymond Hettinger
Terry J. Reedy
Mark Lawrence added the comment:
Has the Argument Clinic had an impact on this or is that a different kettle of fish?
----------
nosy: +BreamoreBoy
versions: +Python 3.4, Python 3.5 -Python 3.1
_______________________________________
Python tracker
Change by Mark Lawrence
participants (6)
-
Georg Brandl
-
Jyrki Pulliainen
-
Mark Lawrence
-
Raymond Hettinger
-
Terry J. Reedy
-
Éric Araujo