On Feb 8, 4:03 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
> When signal is caught handle_shutdown_signal is called. At that point
> SHUTDOWN_PERFORMED will ALWAYS be False. Normally all you do in this function
> is to set SHUTDOWN_PERFORMED to True and have a test somewhere in your main
> program
On Feb 8, 4:03 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
> When signal is caught handle_shutdown_signal is called. At that point
> SHUTDOWN_PERFORMED will ALWAYS be False. Normally all you do in this function
> is to set SHUTDOWN_PERFORMED to True and have a test somewhere in your main
> program
[EMAIL PROTECTED] wrote:
> On Feb 8, 7:04 am, Larry Bates <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] wrote:
>>> I'm developing a program that runs using an asyncore loop. Right now
>>> I can adequately terminate it using Control-C, but as things get
>>> refined I need a better way to stop it.
On Feb 8, 7:04 am, Larry Bates <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > I'm developing a program that runs using an asyncore loop. Right now
> > I can adequately terminate it using Control-C, but as things get
> > refined I need a better way to stop it. I've developed another
> >
[EMAIL PROTECTED] wrote:
> I'm developing a program that runs using an asyncore loop. Right now
> I can adequately terminate it using Control-C, but as things get
> refined I need a better way to stop it. I've developed another
> program that executes it as a child process using popen2.Popen4().
I'm developing a program that runs using an asyncore loop. Right now
I can adequately terminate it using Control-C, but as things get
refined I need a better way to stop it. I've developed another
program that executes it as a child process using popen2.Popen4(). I
was attempting to use signals
