Control-C on Unix misbehaviour?

[Quinn Dunkan]

On Mon, 18 Oct 1999 15:47:52 +0200, flight at mathi.uni-heidelberg.de
<flight at mathi.uni-heidelberg.de> wrote:
>This is a thing I noticed some time ago and was about to enter into the
>Python Bug Database. It's been recorded in the Debian Bug Tracking system
>since some time:
>
>- Debian Bug#24605: python-base: signal handling problems
>  (http://www.debian.org/Bugs/db/24/24605.html)
>- Debian Bug#45929: python: ^C acts as ^D instead of raising a
>  KeyboardInterrupt exception while working within the interactive interpreter.
>  (http://www.debian.org/Bugs/db/45/45929.html)
>
>I'll add a few more data points here for different Linux flavors, all of
>them running on i386 machines:
>
>(A) Debian GNU/Linux 2.1: python 1.5.1-7, libreadlineg2 2.1-12,
>          libc6 2.0.7.19981211
>(B) Debian GNU/Linux 2.1 like above, but running python 1.5.2-5slink-1.
>(C) Debian potato: python 1.5.2-6, libreadlineg2 2.1-13.6,
>          libc6 2.1.2-5
>(D) SuSE Linux 6.1: python-1.5.1-44, libc-99.4.4-0, no readline module
>          (Like Debian 2.1, SuSE 6.1 is running libc6 2.0.7)
>(E) SuSE Linux 6.1: like above, but running Debian's python 1.5.2-6 package.

Here's a data point for Irix6:
If you hit ^C at the >>> prompt with readline loaded (python 1.5), python
stops responding.  Further ^Cs do nothing, in fact the only way I've found
to get out is to kill from another shell or hit ^z kill %.