[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

2021-10-21 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> wont fix stage: -> resolved status: open -> closed superseder: asyncore.dispatcher.recv doesn't handle EAGAIN / EWOULDBLOCK -> Close asyncore/asynchat/smtpd issues and list them here ___ Python tracker

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

2018-01-03 Thread STINNER Victor
STINNER Victor added the comment: I reopen the issue since David Vitek proposed a patch. -- resolution: duplicate -> status: closed -> open ___ Python tracker

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

2018-01-03 Thread David Vitek
David Vitek added the comment: It doesn't look like the fix for issue #16133 fixed this problem, or perhaps it only fixed it for asynchat but not asyncore. I have attached a patch (against python 2, since this is where I needed it fixed). The patch treats WSA flavors

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

2014-07-24 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@gmail.com: -- resolution: - duplicate status: open - closed superseder: - asyncore.dispatcher.recv doesn't handle EAGAIN / EWOULDBLOCK ___ Python tracker rep...@bugs.python.org

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

2014-06-27 Thread STINNER Victor
STINNER Victor added the comment: This issue looks like a duplicate of the issue #16133. -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15982 ___

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

2012-09-20 Thread Nicolai Ehemann
New submission from Nicolai Ehemann: There are some differences between win32 and other os socket implementations. One specific I found is that in windows, non-blocking socket apis will return WSAEWOULDBLOCK or 10035 instead of EWOULDBLOCK. This causes recv() in asyncore.dispatcher to raise