[issue658749] asyncore connect() and winsock errors

2010-08-23 Thread Giampaolo Rodola'
Giampaolo Rodola' added the comment: Fixed in r84284. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Pyt

[issue658749] asyncore connect() and winsock errors

2010-08-21 Thread Mark Lawrence
Changes by Mark Lawrence : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue658749] asyncore connect() and winsock errors

2010-08-21 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' : -- stage: needs patch -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue658749] asyncore connect() and winsock errors

2010-08-21 Thread Giampaolo Rodola'
Giampaolo Rodola' 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 retur

[issue658749] asyncore connect() and winsock errors

2010-08-17 Thread Guido van Rossum
Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue658749] asyncore connect() and winsock errors

2010-08-17 Thread Mark Lawrence
Changes by Mark Lawrence : -- stage: -> needs patch type: -> behavior versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.3 ___ Python tracker ___

[issue658749] asyncore connect() and winsock errors

2009-03-28 Thread intgr
Changes by intgr : -- nosy: +intgr ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mail

[issue658749] asyncore connect() and winsock errors

2008-10-01 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>: -- nosy: +giampaolo.rodola ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bug