giles -- I've just tested it, and although it does seem to be reliable it can take a while for the Ctrl-C to make it to the stuck process.
For instance, if you create a program "busyloop.py":
for i in range(10000):
If you run this from bash (
python3.2 busyloop.py), and immediately hit Ctrl-C, it will be several seconds (and many values of
i) before the
KeyboardInterrupt exception actually takes place (average
i for 10 runs is 2194).
Further testing indicates it's likely just an I/O issue (if I put a
time.sleep call into the above loop my Ctrl-Cs are handled pretty much immediately), so this is probably a pretty minor issue. It might be worth pointing out in the FAQ, though, similar to how you point out the work-around to the Ctrl-Shift-V extra character.