DoEvents equiv?

[Helen Dawson]

Toby Dickenson wrote:

> Carlos Ribeiro <cribeiro at mail.inet.com.br> wrote:
>
> > I write
> >filters for log processing, data format conversion, and so on (big Radius
> >log files just come to my mind :-).
>
> If you dont want to have to worry about GUI-only issues, then dont run
> the scripts inside PythonWin's GUI process.

Unfortunately that answer puts Python on Windows in an annoying
position - having no friendly and reliable debugger. I haven't tried the
`Break into running code' option (perhaps that's new - I last tried PythonWin
six months ago) and I hope it works. Without the "Break into running code'
option the debugging options for Python on Windows are:

PythonWin - too easy to lock up debugger.
IDLE - quirky debugger - breakpoints not supported on Windows last I
checked?
pdb - command line debugger, less efficient for many purposes than a source
level debugger

For most other languages it is quite possible to write command line tools
without worrying about Windows. The VC++ debugger, for instance,
doesn't lockup if a program is debugging locks up or crashes, because they
are separate processes. Forcing command line tool authors to forego a good
debugger or else worry about message pump issues is saying that Python is
not ready for prime time - and I hope that it is.

I wonder if PythonWin should spawn a separate process or thread for the
program it is debugging, instead of for the 'Break into running code' option?

>
> I hope this helps,
>
> Toby Dickenson
> tdickenson at geminidataloggers.com