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 IOError). With this, socket.error > would now inherit from NetworkIOError instead of being its own thing > (the old one didn't even declare a parent!). > > Complete patch attached to the bug. All unit tests pass. > Documentation updates included. > > > http://sourceforge.net/tracker/index.php?func=detail&aid=1706816&group_id=5470&atid=105470 > > Any thoughts? I'm happy with it and would like to commit it if folks > agree. > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org >
-- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
