Antoine Pitrou <pit...@free.fr> added the comment: > > Anyway, my personal opinion is that we should consider the current > > behavior a bug and fix it. I like the idea of setting all accepted > > sockets to blocking mode (and documenting it clearly). > > -1. > > > I think it is what most people would expect. > > Apparently, the designers of BSD thought differently. Remember that > it is them who defined the socket API in the first place, so they > have the right that their design decisions are considered.
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. > We should also take issue10115 into account, which proposes changes > to accept on Linux. One solution might to add optional flags to > accept(), asking for certain behavior variations. Adding flags to control inheritance could be done. But here the problem is that the behaviour is buggy even without assuming the API makes any promise w.r.t. inheritance. (in other words, while issue10115 is a feature request, this issue is really a bug) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7995> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
