RetroSearch Browse

Sun Jan 27 22:26:46 CET 2013 · https://mail.python.org/pipermail/python-dev/2013-January/123733.html

On Sun, 27 Jan 2013 21:56:06 +0100, Ralf Schmitt <ralf at systemexit.de> wrote:
> "R. David Murray" <rdmurray at bitdance.com> writes:
> 
> > On Sun, 27 Jan 2013 19:42:59 +0100, Ralf Schmitt <ralf at systemexit.de> wrote:
> >> Guido van Rossum <guido at python.org> writes:
> >> 
> >> > It's like calling socket.settimeout(0.1) and then complaining that
> >> > urllib.urlopen() raises exceptions
> >> 
> >> but that's not what's happening. you'll see urllib.urlopen raising
> >> exceptions and only afterwards realize that you called into some third
> >> party library code that decided to change the timeout.
> >
> > What is stopping some some third party library code from calling
> > socket.settimeout(0.1)?
> 
> Nothing. That's the point. You just wonder why urlopen fails when the
> global timeout has been changed by that third party library.

Oh, you were agreeing with Guido?  I guess I misunderstood.

--David

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-January/123733.html below:

Choose the default value of the new cloexec parameter