Thank you Thomas, that's helpful. Though I really like the future
interface, I've used it many times while I never used
`multiprocessing.pool.Pool` or its `AsyncResult`. I worry that some of the
expectations I've grown to have from `Future` objects would be broken here.
It would be nice if this
On Sat, Jun 26, 2021 at 11:59 AM Ram Rachum wrote:
> Do you think it's worthwhile to add this feature to `ProcessPoolExecutor`?
>
*restart_workers* certainly seems worth further investigation and
consideration. However, you may also be able to find a workaround using the
*initialzer* argument
And it's on Python stdlib 3
https://docs.python.org/3/library/multiprocessing.html#multiprocessing.pool.Pool
On Sat, 26 Jun 2021, 17:24 Thomas Grainger, wrote:
> billiard a multiprocessing py2 fork/backport has
>
billiard a multiprocessing py2 fork/backport has
https://billiard.readthedocs.io/en/latest/library/multiprocessing.html#multiprocessing.pool.multiprocessing.Pool
with maxtasksperchild
On Sat, 26 Jun 2021, 16:57 Ram Rachum, wrote:
> Hi guys,
>
> I want to have a version of
