This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients eryksun, jnoller, mallyvai, pakal, tim.peters
Date 2017-04-02.03:02:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491102163.95.0.00769172578278.issue5906@psf.upfronthosting.co.za>
In-reply-to
Content
Again, I don't care about orphans.  In the usual cases people are running code with no concern about what happens in case of forced termination.  The only thing stopping it now is that the code goes out of its way to prevent it (or, alternatively, goes out of its way to force Pool workers to be daemonic).  So, e.g., people publish recipes for replacing multiprocessing.Pool to remove this restriction, like here:

http://stackoverflow.com/questions/6974695/python-process-pool-non-daemonic/8963618#8963618
History
Date User Action Args
2017-04-02 03:02:43tim.peterssetrecipients: + tim.peters, jnoller, pakal, mallyvai, eryksun
2017-04-02 03:02:43tim.peterssetmessageid: <1491102163.95.0.00769172578278.issue5906@psf.upfronthosting.co.za>
2017-04-02 03:02:43tim.peterslinkissue5906 messages
2017-04-02 03:02:43tim.peterscreate