Raghuram Devarakonda <draghu...@gmail.com> added the comment: > I am not sure I understand: currently Ctrl-C generates a > KeyboardInterrupt, which can be caught by the application which can > then decide how to proceed (in particular it can start another command > loop or exit with a meaningful message or anything else). > > This patch would suppress KeyboardInterrupt and thus interfere with such > applications. Or am I missing something?
I checked the patch and tested with python from trunk. You are right that the patch catches KeyboardInterrupt thus interfering with any applications that expect it to be propagated upstream. Perhaps, this can be made conditional so that we can keep both behaviors. But CTRL-D processing doesn't suffer from any backwards compatible issues and that part of the patch should be able to be applied safely. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1294> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
