[issue5906] Risk of confusion in multiprocessing module - daemonic processes

[Tim Peters]

Tim Peters added the comment:

@Eryk, not me ;-)  I find the "daemonic or not?" distinction useless for processes - it just gets in the way at times (e.g., a Pool worker dies with an assert(!) error if it tries to create its own Pool for something).

I don't care about orphans either.

It's one reason `concurrent.futures.ProcessPoolExecutor` is sometimes more attractive (it has no "daemon" concept, the processes it creates don't vanish midstream at sometimes surprising times, and neither do they refuse to create additional cf process pools).

----------

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