pythonwin woes

[Kylotan]

Mark Hammond <mhammond at skippinet.com.au> wrote in message news:<bveron$1h6n$1 at arachne.labyrinth.net.au>...

> IDLE runs all programs in a new, external Python process, so never sees 
> this issue.  In lots of ways, I like the way Pythonwin does it - keeping 
> that state around can be very useful - eg, after the program has 
> terminated, you can still see the objects etc.

IDLE keeps the state around after program termination too, so that you
can query it from the command line. It just gets rid of it when you
execute the next program (or re-execute the current one).

-- 
Ben Sizer