Message236332
Interesting! The documentation in 3.4 as well as 2.7 indicates that the keyword should be 'blocking' yet the code implements this as 'block'.
Code to reproduce empirically what is actually implemented:
import multiprocessing
dummy_lock = multiprocessing.Lock()
dummy_lock.acquire(blocking=False) # Raises a TypeError on invalid keyword
The same code changed to 'block=False' works happily.
The code should be changed to reflect the docs and a test probably added too that both exercises this keyword explicitly by name and tests to see if we've fallen out of sync with the threading module. |
|
Date |
User |
Action |
Args |
2015-02-20 21:27:45 | davin | set | recipients:
+ davin, sbt, td |
2015-02-20 21:27:45 | davin | set | messageid: <1424467665.22.0.370746224886.issue23484@psf.upfronthosting.co.za> |
2015-02-20 21:27:45 | davin | link | issue23484 messages |
2015-02-20 21:27:45 | davin | create | |
|