Message 46074 - Python tracker

➜

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	gvanrossum
Recipients
Date	2004-06-22.02:59:41
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=6380 Ideally, ^C should always cause the signal handler for SIGINT to be called, and the KeyboardInterrupt should be generated by the default SIGINT handler. For 2.3, keeping whatever semantics ^C from readline has at the moment should be preserved -- we only want bugfixes, not new features... What else did you want from me? (I'm also lacking focus, or at least time to think about this stuff in detail.)

Logged In: YES 
user_id=6380

Ideally, ^C should always cause the signal handler for
SIGINT to be called, and the KeyboardInterrupt should be
generated by the default SIGINT handler.

For 2.3, keeping whatever semantics ^C from readline has at
the moment should be preserved -- we only want bugfixes, not
new features...

What else did you want from me? (I'm also lacking focus, or
at least time to think about this stuff in detail.)

History
Date	User	Action	Args
2007-08-23 15:37:55	admin	link	issue960406 messages
2007-08-23 15:37:55	admin	create