On Tue, May 28, 2013 at 3:49 PM, Dave Angel wrote:
> I don't use Windows, but I doubt if there's a separate exception
> type for 10057.
Windows sockets error codes at or above 1 aren't mapped to POSIX
error codes. Instead errno is set directly from winerror. So there's
no reason to look at wi
On 28.05.2013 21:37, sparkle Plenty wrote:
If I use an if statement, I cannot use continue after I do my error
handling, so I am really trying to use the except errorname: instead of an
if statement.
I think you haven't understood the code snippet I've posted. The
if-statement is inside the ex
On 05/28/2013 03:37 PM, sparkle Plenty wrote:
If I use an if statement, I cannot use continue after I do my error
handling,
The presence of an if statement cannot affect whether or not a continue
can work. If you give a concrete code example, somebody will be able to
identify the confusion.
If I use an if statement, I cannot use continue after I do my error
handling, so I am really trying to use the except errorname: instead of an
if statement. Therefore, I have to find the correct error name to identify
the 10057 condition to the interpreter, but thanks anyway, Andreas.
On Tue, Ma
On 28.05.2013 19:25, sparkle Plenty wrote:
I need to catch and handle 10057 exceptions when they occur and keep
running. I know 10057 is a WinError, which is a subset of OSError, I
just can't find the right syntax for it. I would appreciate some
help on this one.
I have neither Windows nor Py
