➜

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 loewis
Recipients Justin.Cappos, bbangert, exarkun, giampaolo.rodola, loewis, ned.deily, nicdumz, pitrou, ronaldoussoren, roysmith
Date 2010-11-21.20:16:03
SpamBayes Score 4.416955e-05
Marked as misclassified No
Message-id <4CE97E02.1040401@v.loewis.de>
In-reply-to <1290368740.3620.37.camel@localhost.localdomain>
Content 
> We are talking about the timeout feature, which is a Python feature, not
> a BSD (or Linux) sockets feature. It should work properly, even if that
> means adding some boilerplate around system calls.

I agree that the semantics of the socket timeout API is confusing (and I
wish it had not been added in the first place). However, making it work
"better" must not cause breakage to other legitimate applications.
History
Date User Action Args
2010-11-21 20:16:05loewissetrecipients: + loewis, ronaldoussoren, exarkun, roysmith, pitrou, giampaolo.rodola, ned.deily, nicdumz, bbangert, Justin.Cappos
2010-11-21 20:16:03loewislinkissue7995 messages
2010-11-21 20:16:03loewiscreate