[issue11265] asyncore does not check for EAGAIN and EPIPE errno

2011-03-03 Thread Марк Коренберг
Марк Коренберг added the comment: > I did not catch EAGAIN in connect() as it makes hang some tests. maybe incorrect tests? which test(s) failed ? mmarkk@fad:/usr/include$ fgrep EWOULDB -r . ./asm-generic/errno.h:#define EWOULDBLOCK EAGAIN /* Operation would block */ So not catching EA

[issue11265] asyncore does not check for EAGAIN and EPIPE errno

2011-03-03 Thread Giampaolo Rodola'
Giampaolo Rodola' added the comment: Fixed in r88722. I did not catch EAGAIN in connect() as it makes hang some tests. -- resolution: -> fixed status: open -> closed versions: -Python 2.6 ___ Python tracker

[issue11265] asyncore does not check for EAGAIN and EPIPE errno

2011-03-01 Thread Josiah Carlson
Josiah Carlson added the comment: Giampaolo pinged me over email... These additional conditions look good, and should be targeted for 3.3 . Thank you :) -- nosy: +josiahcarlson ___ Python tracker ___

[issue11265] asyncore does not check for EAGAIN and EPIPE errno

2011-03-01 Thread Giampaolo Rodola'
Giampaolo Rodola' added the comment: Ok for EAGAIN. I'm not completely sure about EPIPE on recv() as it is not listed here: http://www.kernel.org/doc/man-pages/online/pages/man2/recv.2.html ...although I think it's ok to treat it as an alias for connection lost anyway. In pyftpdlib I treat bot

[issue11265] asyncore does not check for EAGAIN and EPIPE errno

2011-03-01 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- assignee: -> giampaolo.rodola nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mail

[issue11265] asyncore does not check for EAGAIN and EPIPE errno

2011-03-01 Thread Марк Коренберг
Марк Коренберг added the comment: patch updated for handling EPIPE -- title: asyncore does not check for EAGAIN errno -> asyncore does not check for EAGAIN and EPIPE errno Added file: http://bugs.python.org/file20964/z.patch ___ Python tracker