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 r.david.murray
Recipients Sworddragon, ezio.melotti, r.david.murray
Date 2013-08-26.15:47:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377532047.28.0.248688658073.issue18836@psf.upfronthosting.co.za>
In-reply-to
Content
Then you catch KeyboardInterrupt and present your alternate text.  I'm not following what the problem is. In particular, once you've caught KeyboardInterrupt, a second ctl-C *should* cause a normal program break, otherwise you've locked the user into a infinite loop he can't get out of if your program logic is wrong.
History
Date User Action Args
2013-08-26 15:47:27r.david.murraysetrecipients: + r.david.murray, ezio.melotti, Sworddragon
2013-08-26 15:47:27r.david.murraysetmessageid: <1377532047.28.0.248688658073.issue18836@psf.upfronthosting.co.za>
2013-08-26 15:47:27r.david.murraylinkissue18836 messages
2013-08-26 15:47:27r.david.murraycreate