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
On Wed, 05 Jan 2011 17:21:23 -0500
Terry Reedy tjre...@udel.edu wrote:
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
On 1/5/2011 5:43 PM, Antoine Pitrou wrote:
On Wed, 05 Jan 2011 17:21:23 -0500
Terry Reedytjre...@udel.edu wrote:
Thank you for spotting the contradiction; this is now fixed.
I am following your example of looking at checkins.
--
Terry Jan Reedy
