requests.{get,post} timeout
dieter
dieter at handshake.de
Wed Aug 23 03:01:42 EDT 2017
Skip Montanaro <skip.montanaro at gmail.com> writes:
> ...
> Given the semantics of timeouts which percolate up from the socket
> level, I agree with Chris. It has a particular meaning, that
> implemented by the underlying socket layer. Unfortunately, the word
> "timeout" can take on related (but different) meanings, depending on
> context.
That's why the documentation (you have cited in your original post)
clearly distinguished between "connect" and "read" timeout - and
thereby explains that only those types of timeouts are supported.
As you explained, those timeouts directly derive from the socket layer
timeouts.
More information about the Python-list
mailing list