[issue658749] asyncore connect() and winsock errors

[Giampaolo Rodola']

Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

The only windows-related error on connect() should be EINVAL
>From http://msdn.microsoft.com/en-us/library/ms737625 :

> WSAEALREADY
> A nonblocking connect call is in progress on the specified socket.

The same approach is adopted by Twisted which just returns in that case.
A patch is in attachment.
Assigning the issue to me as a reminder to commit the patch if no further comments are submitted in the next days.

----------
assignee: josiahcarlson -> giampaolo.rodola
keywords: +patch
Added file: http://bugs.python.org/file18597/asyncore-winerrors.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue658749>
_______________________________________