On Sun, 31 Jul 2011 17:17:00 +0100 Michael Foord <fuzzy...@voidspace.org.uk> wrote: > > I found that [, timeout] bit odd too. But is not mentioning that as > > timeout=None when it is timeout=socket._GLOBAL_DEFAULT_TIME > > technically inaccurate? > > > > It does mean that users will expect to be able to call with an explicit > timeout=None and get the default behaviour. Just use the numeric value of the > global timeout perhaps?
The global timeout is controllable at runtime through socket.setdefaulttimeout(). That's the whole point of using an opaque sentinel. Regards Antoine. _______________________________________________ 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/archive%40mail-archive.com
