[Python-Dev] KeyboardInterrupt on Windows

[Tim Peters]

[Guido]
> I received this problem report (Kurt is the IDLEFORK developer).  Does
> anybody know what could be the matter here?  What changed recently???

Looks like eval-loop optimizations.  The first version essentially compiles
to a JUMP_ABSOLUTE to itself

        >>   10 JUMP_ABSOLUTE           10

and

		case JUMP_ABSOLUTE:
			JUMPTO(oparg);
			goto fast_next_opcode;

This skips the ticker checks, so never checks for interrupts.  As usual, I
expect we can blame Raymond Hettinger's good intentions <wink>.

> ------- Forwarded Message
>
> Date:    Fri, 30 May 2003 15:50:15 -0400
> From:    kbk@shore.net (Kurt B. Kaiser)
> To:      Guido van Rossum <guido@python.org>
> Subject: KeyboardInterrupt
>
> I find that
>
>        while 1: pass
>
> doesn't respond to a KeyboardInterrupt on Python2.3b1 on either
> WinXP or W2K.  Is this generally known?  I couldn't find any mention
> of it.
>
>       while 1: a = 0
>
> is fine on 2.3b1, and both work on Python2.2.
>
> - --
> KBK
>
> ------- End of Forwarded Message