On 27 Jun 2003, Jeremy Hylton wrote:
There's a long standing, hard to reproduce bug report about httplib -- 666219 -- that got me looking at the socket timeout code today. The most basic question I have is: Do we expect the timeout code to work with the httplib module? The original timeoutsocket module uses httplib as an example of its use.
I know for a fact that httplib is currently broken with regard to timeouts and keyboard interrupts on SSL sockets, and wouldn't be at all surprised if it was for normal transfers too. As for the error you are seeing, EALREADY is usually the result of two calls to connect() that are racing each other. Finding out why it is being called twice will likely lead to an obvious solution.