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, rosslagerwall, roysmith
Date 2011-01-04.22:51:14
SpamBayes Score 7.27505e-06
Marked as misclassified No
Message-id <4D23A461.9050409@v.loewis.de>
In-reply-to <1294180186.3669.23.camel@localhost.localdomain>
Content
> Well, either the defaulttimeout should have the priority over the parent
> socket's settings (your argument in msg125135), or it shouldn't. I'm
> fine with both, but I think any more complicated combination would end
> up puzzling for the user :)

Applying the default timeout if set is fine, and I agree it should have
precedence. In case no default timeout is configured, the platform
semantics should prevail. This is tradition in Python: when we define
some behavior (i.e. default timeout), we are entitled to consistently
define all aspects of it. In the other places we use the platform
semantics (leaning towards standards such as POSIX in case the platform
offers alternative semantics).
History
Date User Action Args
2011-01-04 22:51:16loewissetrecipients: + loewis, ronaldoussoren, exarkun, roysmith, pitrou, giampaolo.rodola, ned.deily, nicdumz, bbangert, Justin.Cappos, rosslagerwall
2011-01-04 22:51:14loewislinkissue7995 messages
2011-01-04 22:51:14loewiscreate