On Wed, Jul 04, 2007 at 11:03:42AM +0200, Guido van Rossum wrote:
> Why not simply inherit socket.error from EnvironmentError?
True, that would be simpler; is it enough? If we avoid adding the new
exception, I really think it should inherit from IOError, not
EnviromnentError because sockets are I
Hi,
One of the tracker items: 735515 mentions that urllib should cache 301 and 302
redirections.
urllib / urllib2 should cache the results of 301
(permanent) redirections. This shouldn't break
anything, since it's just an internal optimisation
from one point of view -- but it's also what the
RFC (
A c.l.p discussion referenced from Python-URL just brought this topic
back to my attention, and with the relatively low traffic on the
development lists in the last few days, it seemed like a good time to
repost this PEP (it vanished beneath the Unicode identifier discussion
last time).
Cheers
On Tue, 3 Jul 2007 23:58:44 -0700, "Gregory P. Smith" <[EMAIL PROTECTED]> wrote:
>In response to bug 1706815 and seeing messy code to catch errors in
>network apps I've implemented most of the ideas in the bug and added a
>NetworkIOError exception (child of IOError). With this, socket.error
>would
Why not simply inherit socket.error from EnvironmentError?
On 7/4/07, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
> In response to bug 1706815 and seeing messy code to catch errors in
> network apps I've implemented most of the ideas in the bug and added a
> NetworkIOError exception (child of IOEr
In response to bug 1706815 and seeing messy code to catch errors in
network apps I've implemented most of the ideas in the bug and added a
NetworkIOError exception (child of IOError). With this, socket.error
would now inherit from NetworkIOError instead of being its own thing
(the old one didn't e
