Yeah, so the answer to all this is that 3rd party libraries know better
than to mess with global settings.
On Mon, Jan 28, 2013 at 1:27 PM, Ralf Schmitt
"R. David Murray"
writes: "R. David Murray"
writes: On Sun, 27 Jan 2013 19:42:59 +0100, Ralf Schmitt
wrote: Guido van Rossum
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
On Sun, 27 Jan 2013 21:56:06 +0100, Ralf Schmitt
wrote: 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.
no. I think it's rather surprising if your code depends on some global variable that might change by calling into some third party code. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (python.org/~guido)