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 Julien.Palard
Recipients Julien.Palard, martin.panter
Date 2015-06-24.12:46:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1435149980.39.0.821865546571.issue24486@psf.upfronthosting.co.za>
In-reply-to
Content
OK, so, requests have a `timeout` and take it into account, and it solves my problem.

Yet I don't understand one little thing:

With both requests `timeout` parameter set or unset, the exact same http.client.py:_read_status call the same socket.readinto. With a `request` `timeout`, the socket.readinto uses the recvfrom syscall, but with a `request` `timeout`, readinto uses a `poll` syscall with the given timeout.

The root of the problem is that urllib3 ignores the `socket` `defaulttimeout`, I opened a ticket on this:

https://github.com/shazow/urllib3/issues/655#issuecomment-114835279

So this ticket can be considered closed.
History
Date User Action Args
2015-06-24 12:46:20Julien.Palardsetrecipients: + Julien.Palard, martin.panter
2015-06-24 12:46:20Julien.Palardsetmessageid: <1435149980.39.0.821865546571.issue24486@psf.upfronthosting.co.za>
2015-06-24 12:46:20Julien.Palardlinkissue24486 messages
2015-06-24 12:46:20Julien.Palardcreate