[issue1161031] Neverending warnings from asyncore
Josiah Carlson
report at bugs.python.org
Tue Mar 31 20:16:33 CEST 2009
Josiah Carlson <josiahcarlson at users.sourceforge.net> added the comment:
You are right. Handling OOB data is within the "exceptional condition"
that the select document specifies.
I've added a check for error conditions within handle_expt_event(),
which induces a handle_close() on discovery of an error, handle_expt()
otherwise.
One thing to consider is that when there is OOB data, and when
handle_expt() isn't overridden, we will get churn because that data will
never be read from the socket. I'm thinking about tossing a
handle_close() as part of the default handle_expt() call.
Attached is an updated patch without the handle_close() in
handle_expt().
----------
Added file: http://bugs.python.org/file13517/async_no_warn.patch
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue1161031>
_______________________________________
More information about the Python-bugs-list
mailing list