Comments on: multiprocessing.Pool and KeyboardInterrupt http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/ python, programming and other things Mon, 02 Jan 2012 09:21:00 +0000 hourly 1 By: Casey http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-139296 Casey Wed, 08 Jul 2009 07:28:24 +0000 http://jessenoller.com/?p=386#comment-139296 What and how is _terminate_pool supposed to be used? Can you add some more detail? What and how is _terminate_pool supposed to be used? Can you add some more detail?

]]> By: Casey http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-95063 Casey Wed, 08 Jul 2009 02:28:24 +0000 http://jessenoller.com/?p=386#comment-95063 What and how is _terminate_pool supposed to be used? Can you add some more detail? What and how is _terminate_pool supposed to be used? Can you add some more detail?

]]> By: Joe http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-78484 Joe Wed, 17 Jun 2009 10:52:24 +0000 http://jessenoller.com/?p=386#comment-78484 If you change range(2) to range(200) it does not exit correctly. How would you solve this? If you change range(2) to range(200) it does not exit correctly. How would you solve this?

]]> By: jnoller http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-74556 jnoller Tue, 26 May 2009 21:34:57 +0000 http://jessenoller.com/?p=386#comment-74556 Something has changed. The nice messages should be being raised. Something has changed. The nice messages should be being raised.

]]> By: Shimmer http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-74555 Shimmer Wed, 20 May 2009 04:21:10 +0000 http://jessenoller.com/?p=386#comment-74555 I tried your example and got errors without the nice messages as expected:<br><br>None<br>None<br>Traceback (most recent call last):<br> File "testpool.py", line 26, in <module><br> main()<br> File "testpool.py", line 23, in main<br> pool.join()<br> File "C:Python26libmultiprocessingpool.py", line 340, in join<br> self._result_handler.join()<br> File "C:Python26libthreading.py", line 634, in join<br> self.__block.wait()<br> File "C:Python26libthreading.py", line 237, in wait<br> waiter.acquire()<br>KeyboardInterrupt I tried your example and got errors without the nice messages as expected:

None
None
Traceback (most recent call last):
File “testpool.py”, line 26, in <module>
main()
File “testpool.py”, line 23, in main
pool.join()
File “C:Python26libmultiprocessingpool.py”, line 340, in join
self._result_handler.join()
File “C:Python26libthreading.py”, line 634, in join
self.__block.wait()
File “C:Python26libthreading.py”, line 237, in wait
waiter.acquire()
KeyboardInterrupt

]]> By: Aki http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-63838 Aki Thu, 29 Jan 2009 18:08:11 +0000 http://jessenoller.com/?p=386#comment-63838 Interesting.<br>I did it differently.<br>I disabled SIGINT to any child process using signal.signal(signal.SIGINT, signal.SIG_IGN)<br>The parent takes SIGINT then send a message (or set an event) to each child asking it to shoudown. Interesting.
I did it differently.
I disabled SIGINT to any child process using signal.signal(signal.SIGINT, signal.SIG_IGN)
The parent takes SIGINT then send a message (or set an event) to each child asking it to shoudown.

]]> By: jnoller http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-63219 jnoller Wed, 14 Jan 2009 18:40:27 +0000 http://jessenoller.com/?p=386#comment-63219 See the main post. A keyboard interrupt is not handled the same as other exceptions. At least in py2.5-forward the solution in my main blog post works. See the main post. A keyboard interrupt is not handled the same as other exceptions. At least in py2.5-forward the solution in my main blog post works.

]]> By: gaius.julius http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-63218 gaius.julius Wed, 14 Jan 2009 18:32:03 +0000 http://jessenoller.com/?p=386#comment-63218 anyways, what should I do to gracefully handle KeyboardInterrupt and other similar cases when using Pool? anyways, what should I do to gracefully handle KeyboardInterrupt and other similar cases when using Pool?

]]> By: jnoller http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-62757 jnoller Fri, 09 Jan 2009 17:00:12 +0000 http://jessenoller.com/?p=386#comment-62757 See below: exceptions within the children are handled properly in some cases. See below: exceptions within the children are handled properly in some cases.

]]> By: Jean-Paul http://jessenoller.com/2009/01/08/multiprocessingpool-and-keyboardinterrupt/comment-page-1/#comment-62756 Jean-Paul Fri, 09 Jan 2009 16:38:08 +0000 http://jessenoller.com/?p=386#comment-62756 Great. :) Great. :)

]]>