➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients Dude-X, amaury.forgeotdarc, christian.heimes
Date 2007-12-21.09:57:40
SpamBayes Score 0.08269009
Marked as misclassified No
Message-id <1198231061.01.0.865574846343.issue1677@psf.upfronthosting.co.za>
In-reply-to
Content 
I get the same behaviour with python 2.5.1, and even 2.4.4 (on Windows
2000): I hold down Ctrl-C, and after ~30 "KeyboardInterrupt", the
interpreter stops.

So this is not 3.0 specific. What is new in python3.0 is that file
objects are implemented in python, and are much slower.
It is possible that when the key buffer is full, the next Ctrl-C kills
the program. And this is more likely to happen with python3.0.
History
Date User Action Args
2007-12-21 09:57:41amaury.forgeotdarcsetspambayes_score: 0.0826901 -> 0.08269009
recipients: + amaury.forgeotdarc, christian.heimes, Dude-X
2007-12-21 09:57:41amaury.forgeotdarcsetspambayes_score: 0.0826901 -> 0.0826901
messageid: <1198231061.01.0.865574846343.issue1677@psf.upfronthosting.co.za>
2007-12-21 09:57:40amaury.forgeotdarclinkissue1677 messages
2007-12-21 09:57:40amaury.forgeotdarccreate