Killing wxPython process in PythonWin

[Alexander V. Voinov]

Hi,

Neil Hodgson wrote:
> 
> > I hate to tell you this, but except for very, very simple scripts, I never
> > run anything from within Pythonwin or IDLE. If I do run from inside the
> > IDE, (say, to use the debugger), I generally expect I'll have to exit and
> > restart between runs. I've chased too many "bugs" (that were really fixed,
> > but something wasn't reloaded) to trust anything but a fresh start. And
> I'm
> > certainly not going to bother with the bizarre hacks people come up with
> > (eg, to replace the "code" but not the data in "running" instances).
> 
>    Looks like what is needed is a 'run in new environment' option for
> Pythonwin/IDLE. Or in a separate process?

Again, no problems with (nt)emacs. If you are in a hurry, you may even
launch your wxPython app several times though a py-shell, then close it
and reopen. I'm not sure however, about ntemacs in this last point. But
just in a *Python-Output* way, it works excellent. I did though hacked
python-mode.el to enable asychronous execution of the script (like one
used in *compile*), to be able to see Python prints while the app is
running.

Alexander