Interactive vs IDLE

[Aahz Maruch]

In article <mailman.973320387.26434.python-list at python.org>,
Tim Peters <tim_one at email.msn.com> wrote:
>
>There is one irritating but sometimes killer reason I haven't seen mentioned
>by others:  once a Python program starts running under IDLE, all the IDLE
>windows are usually frozen solid until the program completes, or writes
>output to an IDLE window (typically the shell window).  The Tk component
>(which processes window events) is simply locked out for the duration.  This
>includes processing of Ctrl-C, so a long-running Python program can't even
>be interrupted under IDLE -- the worst case of which is a program with an
>infinite loop.  A plain interactive shell remains responsive even in the
>presence of an infinite loop, so is near infinitely preferable to running
>under IDLE if you routinely run infinite loops.

What happens if you do this on a Cray?
-- 
                      --- Aahz (Copyright 2000 by aahz at pobox.com)

Androgynous poly kinky vanilla queer het    <*>     http://www.rahul.net/aahz/
Hugs and backrubs -- I break Rule 6

"I have the heart of a child.  I keep it in a jar on my desk."  --Robert Bloch