RetroSearch Browse

Wed Jan 5 23:21:23 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-January/107250.html

> Issue #7995: When calling accept() on a socket with a timeout, the returned
> socket is now always non-blocking, regardless of the operating system.

Seems clear enough

> +        # Issue #7995: if no default timeout is set and the listening
> +        # socket had a (non-zero) timeout, force the new socket in blocking
> +        # mode to override platform-specific socket flags inheritance.

Slightly confusing

> +        # Issue #7995: when calling accept() on a listening socket with a
> +        # timeout, the resulting socket should not be non-blocking.

Seems to contradict the first. 'sould not be non-blocking' to me means 
'should be blocking', as opposed to 'is now ... non-blocking'.

Terry

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

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

[Python-Dev] [Python-checkins] r87768 - in python/branches/py3k: Lib/socket.py Lib/test/test_socket.py Misc/NEWS