[issue20319] concurrent.futures.wait() can block forever even if Futures have completed
Glenn Langford
report at bugs.python.org
Sun Jan 26 04:35:39 CET 2014
Glenn Langford added the comment:
> It seems more plausible that the locks around the removals are fixing the bug but I don't see how. I'll look into it some more.
It is the locks around the waiter removals that matter; I think there are only formatting changes elsewhere in the patch. The reason the locks make a difference is that there can be a race condition if multiple wait() calls compete to modify the f._waiters list.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20319>
_______________________________________
More information about the Python-bugs-list
mailing list