Charles Cazabon wrote:
> It might also be nice if the modules that rely on blocking mode being set
> on sockets (basically anything using socket.ssl()) actually explicitly set
> that
> first. Right now, if you do socket.setdefaulttimeout() to a non-None
> value and then try to use anything that d
Steve Holden wrote:
> Jim Fulton wrote:
>
>>Yesterday, I needed to make a web request in a program (actually a test)
>>that could block indefinately, so I needed to set a socket timeout.
>>Unfortunately, AFAICT none of urllib, urllib2, httplib provide options to set
>>the timeout on the sockets th
Steve Holden <[EMAIL PROTECTED]> wrote:
> Jim Fulton wrote:
> > Yesterday, I needed to make a web request in a program (actually a test)
> > that could block indefinately, so I needed to set a socket timeout.
> > Unfortunately, AFAICT none of urllib, urllib2, httplib provide options to
> > set
> >
Jim Fulton wrote:
> Yesterday, I needed to make a web request in a program (actually a test)
> that could block indefinately, so I needed to set a socket timeout.
> Unfortunately, AFAICT none of urllib, urllib2, httplib provide options to set
> the timeout on the sockets they use. I ended up havin
Yup. I just went through a similar exercise with urllib2. It wasn't
too hard to plumb through a different HTTPHandler that set the
timeout, but it would be much nicer as a default option. It seems
like a 30 minute project; might fit in an "odds and ends" sprint.
Jeremy
On 12/22/05, Jim Fulton
Yesterday, I needed to make a web request in a program (actually a test)
that could block indefinately, so I needed to set a socket timeout.
Unfortunately, AFAICT none of urllib, urllib2, httplib provide options to set
the timeout on the sockets they use. I ended up having to roll my own
code to
