On 3/19/11 4:17 PM, John L. Stephens wrote:
On 3/18/2011 7:54 PM, Jason Grout wrote:
Right; thanks. Let me rephrase my questions:
1. Why is important that the multiprocessing Pool worker processors
have daemon=True (I think this is the same as asking: why is it
important that they be terminate
On 3/18/2011 7:54 PM, Jason Grout wrote:
Right; thanks. Let me rephrase my questions:
1. Why is important that the multiprocessing Pool worker processors
have daemon=True (I think this is the same as asking: why is it
important that they be terminated with terminate() rather than join() )?
On 3/18/11 3:29 PM, Ned Deily wrote:
In article<4d838d28.5090...@creativetrax.com>,
Jason Grout wrote:
The problem appears to be that multiprocessing sets its workers to have
the daemon flag set to True, which prevents workers from creating child
processes. If I uncomment the line indicated
In article <4d838d28.5090...@creativetrax.com>,
Jason Grout wrote:
> The problem appears to be that multiprocessing sets its workers to have
> the daemon flag set to True, which prevents workers from creating child
> processes. If I uncomment the line indicated in the code, I can create
> chi
In a recent application, a student of mine tried to create child
processes inside of a multiprocessing Pool worker (for security and
convenience reasons, we wanted to run some code inside of a child
process). Here is some test code for python 2.7:
=
import multipro
