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

Tim Golden mail at timgolden.me.uk
Tue Jun 26 13:28:28 CEST 2012

On 26/06/2012 11:59, Tim Golden wrote:

On 26/06/2012 11:51, Devin Jeanpierre wrote:

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. :) Thanks, Devin. Definitely useful info. AFAICT you haven't added that particular snippet of info to the call. (ie the fact that even one press will trigger the issue). Please feel free to add; I notice that you're the last submitter, some time last year. Goodness knows if I'll get the time, but the natural thing would be to hunt down the uses of SetConsoleCtrlHandler to see what we're doing with them.

OK. We clearly don't set a console handler as I thought we did. Scratch that idea off the list. As Martin said: need to run this with a debugger attached to try to catch in action.

TJG

More information about the Python-Dev mailing list