[issue658749] asyncore connect() and winsock errors

2010-08-23 Thread Giampaolo Rodola'
Giampaolo Rodola' g.rod...@gmail.com added the comment: Fixed in r84284. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue658749 ___

[issue658749] asyncore connect() and winsock errors

2010-08-21 Thread Giampaolo Rodola'
Giampaolo Rodola' g.rod...@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

[issue658749] asyncore connect() and winsock errors

2010-08-21 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' g.rod...@gmail.com: -- stage: needs patch - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue658749 ___ ___

[issue658749] asyncore connect() and winsock errors

2010-08-21 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue658749 ___ ___

[issue658749] asyncore connect() and winsock errors

2010-08-17 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- stage: - needs patch type: - behavior versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue658749

[issue658749] asyncore connect() and winsock errors

2010-08-17 Thread Guido van Rossum
Changes by Guido van Rossum gu...@python.org: -- nosy: -gvanrossum ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue658749 ___ ___ Python-bugs-list

[issue658749] asyncore connect() and winsock errors

2009-03-28 Thread intgr
Changes by intgr ma...@juffo.org: -- nosy: +intgr ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue658749 ___ ___ Python-bugs-list mailing list