Re: multiprocessing signal defect

2010-10-30 Thread Adam Skutt
On Oct 29, 10:08 am, Adam Tauno Williams wrote: > No, I don't think so.  You're asking the module to over generalize > behavior.  Reaping of the child is important, and that the child needs > to be reaped may matter to the master child (why? did something go > wrong?). And such information is made

Re: multiprocessing signal defect

2010-10-29 Thread Neal Becker
Antoine Pitrou wrote: > On Fri, 29 Oct 2010 08:12:19 -0400 > Neal Becker wrote: >> Seems multiprocessing doesn't behave well with signals: >> [...] > > By the way, could you post an issue on the tracker with instructions on > how to reproduce (including OS)? > > Thanks > > Antoine. http://bug

Re: multiprocessing signal defect

2010-10-29 Thread Antoine Pitrou
On Fri, 29 Oct 2010 08:12:19 -0400 Neal Becker wrote: > Seems multiprocessing doesn't behave well with signals: > [...] By the way, could you post an issue on the tracker with instructions on how to reproduce (including OS)? Thanks Antoine. -- http://mail.python.org/mailman/listinfo/python-l

Re: multiprocessing signal defect

2010-10-29 Thread Adam Tauno Williams
On Fri, 2010-10-29 at 07:31 -0700, Jean-Paul Calderone wrote: > On Oct 29, 10:08 am, Adam Tauno Williams > wrote: > > signal handler to do something smart in the case of a "-15" [for which > > there isn't really a thread equivalent - can you sent a SystemV style > > signal to an individual thread

Re: multiprocessing signal defect

2010-10-29 Thread Jean-Paul Calderone
On Oct 29, 10:08 am, Adam Tauno Williams wrote: > signal handler to do something smart in the case of a "-15" [for which > there isn't really a thread equivalent - can you sent a SystemV style > signal to an individual thread in a process?  I don't think so.] Yes. pthread_kill(P) Jean-Paul --

Re: multiprocessing signal defect

2010-10-29 Thread Antoine Pitrou
On Fri, 29 Oct 2010 10:08:01 -0400 Adam Tauno Williams wrote: > > No, I don't think so. You're asking the module to over generalize > behavior. Reaping of the child is important, and that the child needs > to be reaped may matter to the master child (why? did something go > wrong?). Silently r

Re: multiprocessing signal defect

2010-10-29 Thread Adam Tauno Williams
On Fri, 2010-10-29 at 08:39 -0400, Neal Becker wrote: > Adam Tauno Williams wrote: > > > On Fri, 2010-10-29 at 08:12 -0400, Neal Becker wrote: > >> Seems multiprocessing doesn't behave well with signals: > >> - > >> from multiprocessing import Pool > >> import time > >> def sleep (dummy):

Re: multiprocessing signal defect

2010-10-29 Thread Neal Becker
Adam Tauno Williams wrote: > On Fri, 2010-10-29 at 08:12 -0400, Neal Becker wrote: >> Seems multiprocessing doesn't behave well with signals: >> - >> from multiprocessing import Pool >> import time >> def sleep (dummy): >> time.sleep (10) >> if __name__ == '__main__': >> pool = Poo

Re: multiprocessing signal defect

2010-10-29 Thread Adam Tauno Williams
On Fri, 2010-10-29 at 08:12 -0400, Neal Becker wrote: > Seems multiprocessing doesn't behave well with signals: > - > from multiprocessing import Pool > import time > def sleep (dummy): > time.sleep (10) > if __name__ == '__main__': > pool = Pool (processes=2) > result = po