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-22.00:25:04
SpamBayes Score 2.45961e-08
Marked as misclassified No
Message-id <1290385502.3620.46.camel@localhost.localdomain>
In-reply-to <1290384915.08.0.0768166392917.issue7995@psf.upfronthosting.co.za>
Content
> The notes in the documentation under socket.gettimeout() do go into
> more detail than elsewhere.  But at least one thing there is at best
> misleading: "Sockets are always created in blocking mode" is, as we've
> seen, not correct for BSD-ish systems for sockets returned by
> accept().  So, at a minimum, this section and the documentation for
> socket.accept() should be expanded, along with any other changes.

Well, unless someone explains convincingly how the current behaviour is
desireable (rather than misleading and useless), I really think this is
a bug that should be fix (then we can also discuss what the fix should
exactly be).
History
Date User Action Args
2010-11-22 00:25:06pitrousetrecipients: + pitrou, loewis, ronaldoussoren, exarkun, roysmith, giampaolo.rodola, ned.deily, nicdumz, bbangert, Justin.Cappos
2010-11-22 00:25:04pitroulinkissue7995 messages
2010-11-22 00:25:04pitroucreate