[issue39207] concurrent.futures.ProcessPoolExecutor does not properly reap jobs and spawns too many workers

[Kyle Stanley]

Kyle Stanley <aeros167 at gmail.com> added the comment:

> It would certainly be better to start the worker processes on demand. It  probably also requires careful thought about how to detect that more workers are required.

Alright. In that case, I'll do some experimentation when I get the chance and see if I can come up with an effective way to spawn the worker processes as needed, without incurring a significant performance penalty.  

Note: I have a few other projects and obligations in the meantime, so I'm not 100% certain when I'll have the time to work on this. If anyone else is interested in working on this as well, certainly feel free to do so.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue39207>
_______________________________________