[ python-Bugs-658749 ] asyncore connect() and winsock errors
SourceForge.net
noreply at sourceforge.net
Sat Jan 6 23:06:13 CET 2007
Bugs item #658749, was opened at 2002-12-26 13:25
Message generated for change (Settings changed) made by akuchling
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: 2004-03-04 03: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
More information about the Python-bugs-list
mailing list