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 Justin.Cappos, bbangert, exarkun, giampaolo.rodola, loewis, ned.deily, nicdumz, pitrou, ronaldoussoren, roysmith
Date 2010-11-21.20:24:37
SpamBayes Score 7.68989e-08
Marked as misclassified No
Message-id <1290371074.3620.45.camel@localhost.localdomain>
In-reply-to <4CE97E02.1040401@v.loewis.de>
Content
Le dimanche 21 novembre 2010 à 20:16 +0000, Martin v. Löwis a écrit :
> 
> > 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.

Well, I don't think setting a timeout on a listening socket and then
expecting the socket received through accept() to be non-blocking (but
only on BSD) is a legitimate application.
History
Date User Action Args
2010-11-21 20:24:39pitrousetrecipients: + pitrou, loewis, ronaldoussoren, exarkun, roysmith, giampaolo.rodola, ned.deily, nicdumz, bbangert, Justin.Cappos
2010-11-21 20:24:37pitroulinkissue7995 messages
2010-11-21 20:24:37pitroucreate