[Python-Dev] Poking about issue 1677 (original) (raw)

Devin Jeanpierre jeanpierreda at gmail.com
Tue Jun 26 12:51:02 CEST 2012

Hi guys,

I just wanted to bring some more attention to issue #1677 , because I feel it's important and misunderstood. See: http://bugs.python.org/issue1677

The issue is that sometimes, if you press ctrl-c on Windows, instead of raising a KeyboardInterrupt, Python will exit completely. Because of this, any program that relies on ctrl-c/KeyboardInterrupt is not guaranteed to work on windows. Also, working with the interactive interpreter becomes really annoying for those with the habit of deleting the whole input line via ctrl-c.

Some people that read the bug report think that this only happens if you hold down ctrl-c long enough or fast enough or some such thing. That's not so; it can happen just from pressing ctrl-c once. Whatever race condition here is not related to the timing gaps between presses of ctrl-c. The "test cases" of "hold down ctrl-c for a bit" are to conveniently reproduce, not a description of the problem.

Hope this was the right place. #python-dev encouraged me to post here, so, yeah. And thanks for all your hard work making Python a pleasant place to be. :)

-- Devin

More information about the Python-Dev mailing list