[issue9205] Parent process hanging in multiprocessing if children terminate unexpectedly
Antoine Pitrou
report at bugs.python.org
Thu Mar 31 14:25:38 CEST 2011
Antoine Pitrou <pitrou at free.fr> added the comment:
The problem with this approach is that it won't help concurrent.futures.
Detection of killed endpoints should ideally happen at a lower level, e.g. in Process or Queue or Connection objects.
Speaking of which, I wonder why we have both multiprocessing.Pool and concurrent.futures.ProcessPoolExecutor. They seem to fill the exact same needs, with different APIs...
----------
keywords: +easy -patch
versions: +Python 3.2, Python 3.3 -Python 2.6
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9205>
_______________________________________
More information about the Python-bugs-list
mailing list