Hi,
--- Seth Vidal <skvidal@xxxxxxxxxxxxxxxxx> wrote:
> On Thu, 2008-09-11 at 20:33 -0700, CAI Qian wrote:
> > --- CAI Qian <caiqian@xxxxxxxx> wrote:
> >
> > > 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.
> > >
> >
> > The question is, is this the only place that Python fails?
>
> And yet, not an interesting question for this list.
>
I think it is of yum users' interests when making language decision.
There is another example of bad usability for handling CTRL-C,
[root@localhost ~]# yum -d 10 update
Config time: 0.107
Yum Version: 3.2.19
COMMAND: yum -d 10 update
Installroot: /
Reading Local RPMDB
rpmdb time: 0.001
Setting up Package Sacks
pkgsack time: 0.003
Setting up Update Process
Building updates object
^C^C^C^C^C^C^C^C^C^C^C^C^C^C^Cup:Obs Init time: 0.733
^C^Cputting kpathsea in complex update
...
You could see from the above, I have to hit CTRL-C more than 10 times
in order to cancel the operation. Far more than tolerant for reasonable
user experience. Is it the same thing as the Python socket handling
bug?
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
