On Sun, 31 Jul 2011 17:17:00 +0100 Michael Foord <fuzzyman at 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.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4