Re: Re: Horrible response to keyboardInterrupt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

--- Seth Vidal <skvidal@xxxxxxxxxxxxxxxxx> wrote:

> On Thu, 2008-09-11 at 19:32 -0700, CAI Qian wrote:
> 
> > Correct. That is one of situations of bad CTRL-C response. I was
> trying
> > to simulate a network failure or slow connection. It could be quite
> > normal in reality.
> > 
> 
> Great, then please file this  against python.
> 
> $ ipython
> In [1]: import socket
> 
> In [4]: socket.gethostbyname('www.phy.duke.edu')
>
^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C---------------------------------------------------------------------------
> KeyboardInterrupt                         Traceback (most recent call
> last)
> 
> the socket call to gethostbyname does let you do an interrupt in the
> middle of it - or at least - not at all times.
>

I know there must be something wrong with Python.

Cai Qian
 
> 
> -sv
> 
> 
> _______________________________________________
> Yum mailing list
> Yum@xxxxxxxxxxxxxxxxxxxx
> https://lists.dulug.duke.edu/mailman/listinfo/yum
> 

_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxxxxx
https://lists.dulug.duke.edu/mailman/listinfo/yum

[Index of Archives]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux