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.22:57:17
SpamBayes Score 3.49947e-05
Marked as misclassified No
Message-id <4CE9A3CC.3080301@v.loewis.de>
In-reply-to <1290374569.58.0.968912618321.issue7995@psf.upfronthosting.co.za>
Content
> I got into this by starting with Issue7322, which reports a scenario
> where data is lost using makefile().  The docs for makefile() say,
> "The socket must be in blocking mode (it can not have a timeout)".
> So, we've got published documentation which equates non-blocking mode
> with a timeout set.

This wording goes back to r54491, from issue882297. Facundo writes

# If the socket is in blocking mode, it can NOT have a timeout.
# I fixed the docs, and made that explicit.

so I don't think he really meant to equate the two. I'm not a native
speaker (of English), so I'll refrain from proposing an alternative
wording.
History
Date User Action Args
2010-11-21 22:57:19loewissetrecipients: + loewis, ronaldoussoren, exarkun, roysmith, pitrou, giampaolo.rodola, ned.deily, nicdumz, bbangert, Justin.Cappos
2010-11-21 22:57:17loewislinkissue7995 messages
2010-11-21 22:57:17loewiscreate