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 draghuram
Recipients alexandre.vassalotti, draghuram, gvanrossum, isandler, stephbul
Date 2009-11-13.14:56:09
SpamBayes Score 2.5335561e-05
Marked as misclassified No
Message-id <2c51ecee0911130656p7ef6b10cib1d94c37f6c7ed4e@mail.gmail.com>
In-reply-to <1258095607.89.0.897957063221.issue1294@psf.upfronthosting.co.za>
Content
> 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.
History
Date User Action Args
2009-11-13 14:56:12draghuramsetrecipients: + draghuram, gvanrossum, isandler, alexandre.vassalotti, stephbul
2009-11-13 14:56:10draghuramlinkissue1294 messages
2009-11-13 14:56:09draghuramcreate