This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kristjan.jonsson
Recipients kristjan.jonsson, pitrou
Date 2011-03-30.13:05:48
SpamBayes Score 9.38036e-08
Marked as misclassified No
Message-id <1301490349.28.0.158222927222.issue11721@psf.upfronthosting.co.za>
In-reply-to
Content
I cannot see from the link to which branch that was committed, or what revision.  But I assume it is the default branch.  I can confirm that this appears to be fixed.

The corresponding defect has a long (and bothersome) discussion.  I am, however, surprised that this was not considered a "bug" and backported.

The "bug" is pretty clear:  socket.gettimeout() returns None, and yet socket.recv() returns in EWOULDBLOCK.  This is clearly against spec, since the gettimeout() == None means that the socket is supposed to be blocking.

I can agree with the fix (my number 1 suggestion) but I would have liked to see it done in socketmodule.c where the timeout semantics are all defined, rather than as a cludgy special case in socket.py
History
Date User Action Args
2011-03-30 13:05:49kristjan.jonssonsetrecipients: + kristjan.jonsson, pitrou
2011-03-30 13:05:49kristjan.jonssonsetmessageid: <1301490349.28.0.158222927222.issue11721@psf.upfronthosting.co.za>
2011-03-30 13:05:48kristjan.jonssonlinkissue11721 messages
2011-03-30 13:05:48kristjan.jonssoncreate