Pythonwin is terrible!

[Mark Hammond]

"David Bolen" <db3l at fitlinxx.com> wrote in message
news:uog5b4m3e.fsf at ctwd0143.fitlinxx.com...

> In particular, if the code uses broad exception clauses (for example,
> plain "except") in order to attempt recoveries and continue executing,
> then it's going to catch the KeyboardInterrupt exception this method
> tries to generate just as any other exception, and continue execution.
> If that execution is resulting in an infinite loop, well...

Actually, there are 2 things that can make it appear like it doesnt always
work:

* If an infinite loop is continually printing, we may have broken the
loop, but in the process of printing the resulting megabytes generated.
Being patient can solve this.

* The Keyboard interrupt happens, but Pythonwin sees it!  Even though your
code is in the tight loop, Pythonwin is still getting a little involved -
notably again for "print" statements.  So sometimes the break happens _as_
Pythonwin is printing, and Pythonwin just stops printing - but your code
keeps going!

Mark.