Re: waiting on an event blocks all signals

2008-05-18 Thread Rhamphoryncus
On May 18, 9:05 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > alan schrieb: > > > This ignores CTRL-C on every platform I've tested: > > > python -c "import threading; threading.Event().wait()" > > ^C^C^C^C > > > It looks to me like all signals are masked before entering wait(). Can > > someo

Re: waiting on an event blocks all signals

2008-05-18 Thread Diez B. Roggisch
alan schrieb: This ignores CTRL-C on every platform I've tested: python -c "import threading; threading.Event().wait()" ^C^C^C^C It looks to me like all signals are masked before entering wait(). Can someone familiar with the internals explain and/or justify this behavior? Thanks, They aren't

Re: waiting on an event blocks all signals

2008-05-17 Thread alan
On May 17, 3:06 pm, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote: > On Sat, 17 May 2008 12:49:54 -0700, John Schroeder <[EMAIL PROTECTED]> wrote: > >On Sat, May 17, 2008 at 12:32 PM, alan <[EMAIL PROTECTED]> wrote: > > >> This ignores CTRL-C on every platform I've tested: > > >> python -c "import

Re: waiting on an event blocks all signals

2008-05-17 Thread alan grow
On Sat, May 17, 2008 at 2:49 PM, John Schroeder <[EMAIL PROTECTED]> wrote: > ^C only kills the main thread. Use Control-Break to kill all threads. >> >> python -c "import threading; threading.Event().wait()" >> ^C^C^C^C There's a single main thread here though. Or am I missing something? -- http:

Re: waiting on an event blocks all signals

2008-05-17 Thread Jean-Paul Calderone
On Sat, 17 May 2008 12:49:54 -0700, John Schroeder <[EMAIL PROTECTED]> wrote: On Sat, May 17, 2008 at 12:32 PM, alan <[EMAIL PROTECTED]> wrote: This ignores CTRL-C on every platform I've tested: python -c "import threading; threading.Event().wait()" ^C^C^C^C It looks to me like all signals ar

Re: waiting on an event blocks all signals

2008-05-17 Thread John Schroeder
^C only kills the main thread. Use Control-Break to kill all threads. On Sat, May 17, 2008 at 12:32 PM, alan <[EMAIL PROTECTED]> wrote: > This ignores CTRL-C on every platform I've tested: > > python -c "import threading; threading.Event().wait()" > ^C^C^C^C > > It looks to me like all signals a

waiting on an event blocks all signals

2008-05-17 Thread alan
This ignores CTRL-C on every platform I've tested: python -c "import threading; threading.Event().wait()" ^C^C^C^C It looks to me like all signals are masked before entering wait(). Can someone familiar with the internals explain and/or justify this behavior? Thanks, -Alan -- http://mail.python.