Re: Socket exceptions aren't in the standard exception hierarchy (M2Crypto issue)

2007-04-26 Thread John Nagle
On a related note, M2Crypto's exceptions are direct children of Exception. If we add NetworkError, there will be a better place to put them. Currently, you have to catch, at least, M2Crypto.SSL.Checker.SSLVerificationError M2Crypto.SSL.SSLError both of which can

Re: Socket exceptions aren't in the standard exception hierarchy

2007-04-25 Thread Steve Holden
John Nagle wrote: > Steve Holden wrote: >> John Nagle wrote: >> >>> Steve Holden wrote: >>> John Nagle wrote: [socket.error bug report] > >> All these notes should be included in the bug report, as I suspect the >> module would benefit from additional clarity. > > Done. See > >

Re: Socket exceptions aren't in the standard exception hierarchy

2007-04-24 Thread John Nagle
Steve Holden wrote: > John Nagle wrote: > >> Steve Holden wrote: >> >>> John Nagle wrote: >>> [socket.error bug report] > All these notes should be included in the bug report, as I suspect the > module would benefit from additional clarity. Done. See [ 1706815 ] socket.error exceptions

Re: Socket exceptions aren't in the standard exception hierarchy

2007-04-24 Thread Steve Holden
John Nagle wrote: > Steve Holden wrote: >> John Nagle wrote: >> [socket.error bug report] >> Where did you get this information? If true it would certainly need to be logged as a bug, but under Windows on 2,4 I see >>> issubclass(socket.gaierror, Exception) True >>>

Re: Socket exceptions aren't in the standard exception hierarchy

2007-04-24 Thread John Nagle
Steve Holden wrote: > John Nagle wrote: > [socket.error bug report] > >>> >>> Where did you get this information? If true it would certainly need >>> to be logged as a bug, but under Windows on 2,4 I see >>> >>> >>> issubclass(socket.gaierror, Exception) >>> True >>> >>> >>> >>> and the same un

Re: Socket exceptions aren't in the standard exception hierarchy

2007-04-23 Thread Steve Holden
John Nagle wrote: [socket.error bug report] >> >> Where did you get this information? If true it would certainly need to >> be logged as a bug, but under Windows on 2,4 I see >> >> >>> issubclass(socket.gaierror, Exception) >> True >> >>> >> >> and the same under Cygwin 2.5. I am presuming most

Re: Socket exceptions aren't in the standard exception hierarchy

2007-04-23 Thread Daniel Nogradi
> 2. File "D:\Python24\lib\socket.py", line 295, in read > data = self._sock.recv(recv_size) > error: (10054, 'Connection reset by peer') > > >>> That looks like M$ Windows version of UNIX/Linux error number 54 > >>> (pretty much all Windows socket errors are UNIX number+100

Re: Socket exceptions aren't in the standard exception hierarchy

2007-04-23 Thread John Nagle
Steve Holden wrote: > John Nagle wrote: > >> Dennis Lee Bieber wrote: >> >>> On Sun, 22 Apr 2007 23:20:25 -0700, John Nagle <[EMAIL PROTECTED]> >>> declaimed the following in comp.lang.python: >>> >>> 2. File "D:\Python24\lib\socket.py", line 295, in read data = self._sock.recv(recv_size

Re: Socket exceptions aren't in the standard exception hierarchy

2007-04-23 Thread Steve Holden
John Nagle wrote: > Dennis Lee Bieber wrote: >> On Sun, 22 Apr 2007 23:20:25 -0700, John Nagle <[EMAIL PROTECTED]> >> declaimed the following in comp.lang.python: >> >> >>> 2. File "D:\Python24\lib\socket.py", line 295, in read >>> data = self._sock.recv(recv_size) >>> error: (10054, 'Connection re

Re: Socket exceptions aren't in the standard exception hierarchy

2007-04-23 Thread John Nagle
Dennis Lee Bieber wrote: > On Sun, 22 Apr 2007 23:20:25 -0700, John Nagle <[EMAIL PROTECTED]> > declaimed the following in comp.lang.python: > > >>2. File "D:\Python24\lib\socket.py", line 295, in read >>data = self._sock.recv(recv_size) >>error: (10054, 'Connection reset by peer') >> > >