Facundo Batista wrote:
> Steve Holden wrote:
>
>
>>1) There is work afoot to build timeout arguments into network libraries
>>for 2.6, and I know Facundo Batista has been involved, you might want to
>>Google or email Facundo about that.
>
>
> Right now (in svn trunk) httplib, ftplib, telnetli
Steve Holden wrote:
> 1) There is work afoot to build timeout arguments into network libraries
> for 2.6, and I know Facundo Batista has been involved, you might want to
> Google or email Facundo about that.
Right now (in svn trunk) httplib, ftplib, telnetlib, etc, has a timeout
argument.
If y
John Nagle wrote:
> I took a look at Facundo Batista's work in the tracker, and he
> currently seems to be trying to work out a good way to test the
> existing SSL module. It has to connect to something to be tested,
Right now, test_socket_ssl.py has, besides the previous tests, the
capabil
Steve Holden wrote:
> John Nagle wrote:
>> Then we'd have a reasonable network timeout system.
>> We have about half of the above now, but it's not consistent.
>>
>> Comments?
>>
> The only comments I'll make for now are
>
> 1) There is work afoot to build timeout arguments into network libraries
John Nagle wrote:
>I thought I had all the timeout problems with urllib worked around,
> but no.
>
>socket.setdefaulttimeout is useful, but not always effective.
> I'm setting that to 15 seconds.
> If the host end won't open the connection within 15 seconds,
> urllib times out. But if the
I thought I had all the timeout problems with urllib worked around,
but no.
socket.setdefaulttimeout is useful, but not always effective.
I'm setting that to 15 seconds.
If the host end won't open the connection within 15 seconds,
urllib times out. But if the host end opens the connection,
