[issue20319] concurrent.futures.wait() can block forever even if Futures have completed
Sebastian Kreft
report at bugs.python.org
Thu Jun 5 10:24:19 CEST 2014
Sebastian Kreft added the comment:
The Executor is still working (but I'm using a ThreadPoolExcutor). I can dynamically change the number of max tasks allowed, which successfully fires the new tasks.
After 2 days running, five tasks are in this weird state.
I will change the code as suggested and post my results.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20319>
_______________________________________
More information about the Python-bugs-list
mailing list