[Python-Dev] KeyboardInterrupt on Windows (original) (raw)
Jeremy Hylton jeremy@zope.com
30 May 2003 16:43:28 -0400
- Previous message: [Python-Dev] KeyboardInterrupt on Windows
- Next message: [Python-Dev] KeyboardInterrupt on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It's probably an unintended consequence of the "while 1" optimization and the fast-next-opcode optimization. "while 1" doesn't do a test at runtime anymore. And opcodes like JUMP_ABSOLUTE bypass the test for pending exceptions. The next result is that while 1: pass puts the interpreter in a tight loop doing a JUMP_ABSOLUTE that goes nowhere. That is offset X has JUMP_ABSOLUTE X.
I'd be inclined to call this a bug, but I'm not sure how to fix it.
Jeremy
- Previous message: [Python-Dev] KeyboardInterrupt on Windows
- Next message: [Python-Dev] KeyboardInterrupt on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]