[ python-Bugs-658749 ] asyncore connect() and winsock errors

[SourceForge.net]

Bugs item #658749, was opened at 2002-12-26 21:25
Message generated for change (Comment added) made by klimkin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=658749&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Guido van Rossum (gvanrossum)
Assigned to: Josiah Carlson (josiahcarlson)
Summary: asyncore connect() and winsock errors

Initial Comment:
asyncore's connect() method should interpret the
winsock errors; these are different from Unix (and
different between the Win98 family and the Win2k family).

----------------------------------------------------------------------

Comment By: Alexey Klimkin (klimkin)
Date: 2007-01-08 23:59

Message:
Logged In: YES 
user_id=410460
Originator: NO

Sorry, but 2 years ago we were developing this for Linux and XP only;).
Even they say to be POSIX, they behave a little differently. As I remember,
we have added handling of some E* return codes, which was appearing for
non-blocking connect on XP. If you connect while in blocking state, you
won't get those values.

----------------------------------------------------------------------

Comment By: Josiah Carlson (josiahcarlson)
Date: 2007-01-07 09:10

Message:
Logged In: YES 
user_id=341410
Originator: NO

klimkin: Please explain how either of the versions of patch #909005 fix
the problem.  From what I can tell, the only change you made was to move
the accept() handling of errors to the handle_read() method.

Guido: In terms of winsock errors, which are actually raised on connection
error between win98, win2k, and/or XP, 2003, and Vista?

----------------------------------------------------------------------

Comment By: Alexey Klimkin (klimkin)
Date: 2004-03-04 11:24

Message:
Logged In: YES 
user_id=410460

Patch #909005 fixes the problem.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=658749&group_id=5470