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 pitrou
Recipients exarkun, mdcowles, neologix, pitrou
Date 2010-04-26.09:48:47
SpamBayes Score 0.0012608061
Marked as misclassified No
Message-id <1272275328.66.0.51017590771.issue8493@psf.upfronthosting.co.za>
In-reply-to
Content
> That's what I thought at first too. But the user's sockets were set to 
> blocking.

If you set a timeout on a socket, it is really non-blocking internally (from the OS' point of view). So perhaps this is what you are witnessing.

By the way, rather than sleeping a fixed amount of time before retrying, you could probably use select() on the socket.
History
Date User Action Args
2010-04-26 09:48:49pitrousetrecipients: + pitrou, mdcowles, exarkun, neologix
2010-04-26 09:48:48pitrousetmessageid: <1272275328.66.0.51017590771.issue8493@psf.upfronthosting.co.za>
2010-04-26 09:48:47pitroulinkissue8493 messages
2010-04-26 09:48:47pitroucreate