No way to set a timeout in "urllib".

Re: No way to set a timeout in "urllib&qu ot;.


JohnThere's no way to set a timeout if you use "urllib" to open a URL.
John"HTTP", which "urllib" uses, supports this, but the functionality
Johnis lost at the "urllib" level.

John It's not available via "class URLopener" or "FancyURLopener ",
John either.

JohnThere is a non-thread-safe workaround from 2003 at

...

This topic has come up several times since timeouts were added to socket.
Each time we've asked for a patch that adds timeouts in a rational manner to
all the stuff layered on top of the socket module (httplib, ftplib, etc). As
far as I know it's apparently never been important enough for anyone to rise
to the challenge. If I remember next spring perhaps I'll submit it as a
possible Google Summer of Code proposal.

JohnThe correct fix would probably be to add methods to class
JohnURLopener to control this; that's the usual way of handling
Johnspecial URL opening situations.

The correct way would be to deal with it at the httplib level, then
percolate it up to urllib2. Urllib should probably not be extended any
further.

Skip

Re: No way to set a timeout in "urllib&qu ot;.

skip@pobox.com wrote:It ought not to take more than a day or two, although it is annoying
that you have to deal with the problem at several levels.

If you're looking for a Summer of Code project, consider finishing
the Python SSL library, which doesn't even check certificates, let alone
revocation lists. It's a pure interface problem. OpenSSL does all the
hard parts, but the Python glue code is crude and incomplete.

John Nagle

Re: No way to set a timeout in "urllib&qu ot;.


JohnIf you're looking for a Summer of Code project, ...

I'm not. I'm about 25 years out of grad school. ;-)

Skip

Re: No way to set a timeout in "urllib&qu ot;.

John Nagle <nagle@animats. comwrites:
And...? What specifically are you complaining about?

Just as a matter of fact (I'm not grumpy about it): I see from your
message that you already know that there is not a shortage of people
who spot the lack of this kind of feature. The shortage is of people
who will actually do the job of adding the feature -- most
importantly, people who will contribute high quality patches,
including tests and docs, and people who will review other people's
patches.

[...]

While it might be discouraging to be confronted with tiresome
realities of schedules and resources, those are the realities.

The flip side is that you can make a real difference by putting in
some work.

Looking forward to your patch :-)


John