[issue21899] Futures are not marked as completed

Sebastian Kreft report at bugs.python.org
Wed Jul 16 16:56:39 CEST 2014


Sebastian Kreft added the comment:

After more testing I finally found that in fact the process is not being killed. That means that there is no problem with the futures. But instead it is probably related with subprocess deadlocking, as the problematic process does not consume any CPU.

Sorry for the false report.

----------
nosy:  -bquinlan
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21899>
_______________________________________


More information about the Python-bugs-list mailing list