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 Justin.Cappos, bbangert, exarkun, giampaolo.rodola, kristjan.jonsson, loewis, ned.deily, nicdumz, pitrou, ronaldoussoren, rosslagerwall, roysmith, stutzbach
Date 2011-03-30.18:30:33
SpamBayes Score 1.84733e-08
Marked as misclassified No
Message-id <1301509834.25.0.640664703836.issue7995@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine, absolument.  Please see attached file bug.py

As for a different patch, we should agree what behaviour should be expected.  I don't think it is possible to rely on some platform specific behaviour.  This is because it is in general not possible to query the blokcking state of a socket.  Instead we should simply define it for python, and in accordance to established tradition, namely that defaulttimeout prevails.

Btw, defaulttimeout(None) doesn't mean that that there is no default, it means that the default is "blocking."
History
Date User Action Args
2011-03-30 18:30:34kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, ronaldoussoren, exarkun, roysmith, pitrou, giampaolo.rodola, ned.deily, stutzbach, nicdumz, bbangert, Justin.Cappos, rosslagerwall
2011-03-30 18:30:34kristjan.jonssonsetmessageid: <1301509834.25.0.640664703836.issue7995@psf.upfronthosting.co.za>
2011-03-30 18:30:33kristjan.jonssonlinkissue7995 messages
2011-03-30 18:30:33kristjan.jonssoncreate