Control-C on Unix misbehaviour?

[Thomas A. Bryan]

Michael Hudson wrote:

> If I execute:
> 
> [mwh21 at atrus src]$ python -c "raw_input()"
> 
> then type f, f, control-c, control-c (that wierdness I'm used to) I
> get:
> 
> ffTraceback (innermost last):
>   File "<string>", line 1, in ?
> KeyboardInterrupt
> 
> However, if I try
> 
> [mwh21 at atrus src]$ python -c "import readline; raw_input()"
> 
> and hit f, f, and then just one control-c, I get just:
> 
> ff
> 
> and then I'm back to the bash prompt.

Okay.  I tried this on a Red Hat 6.0 machine. 
readline-2.2.1-5
python-1.5.2-2 (from Oliver Andrich's page)
I get the same results as those you report above.

On the Starship, we've got Red Hat 5.2 and a 
Python 1.5.2 that I built from source.  rpm reports
readline-2.2.1-1
On the Starship, your second example doesn't just dump me 
back to the prompt.  I get an uncaught KeyBoard interrupt
after one Control-C.

> python 1.5.2 (both from redhat 6.1 & a fairly recent cvs)
> readline-2.2.1-5 (according rpm -q readline)
....
> Is that enough information to help anyone explain what's going on?
> Anyone experience/not experience the phenomenon (I got one negative
> via email).

Maybe you try it with a different version of readline?  For example, the 
RPM that came with Red Hat 5.2.

---Tom