Message121983
> > 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.
>
>
> Right. But setting the server socket to nonblocking, and then
> expecting the connection socket to also be nonblocking might be.
Okay sure. This is fine. That is why I suggested that if you don't like my patch, one might instead change new Python sockets to inherit the timeout / blocking setting on BSD.
However, I hope we can all agree that having the Python socket object in a different blocking / non-blocking state than the OS socket descriptor is wrong. This is what needs to be fixed. |
|
Date |
User |
Action |
Args |
2010-11-21 20:40:35 | Justin.Cappos | set | recipients:
+ Justin.Cappos, loewis, ronaldoussoren, exarkun, roysmith, pitrou, giampaolo.rodola, ned.deily, nicdumz, bbangert |
2010-11-21 20:40:35 | Justin.Cappos | set | messageid: <1290372035.17.0.457676089087.issue7995@psf.upfronthosting.co.za> |
2010-11-21 20:40:32 | Justin.Cappos | link | issue7995 messages |
2010-11-21 20:40:32 | Justin.Cappos | create | |
|