New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
asynchat's handle_error inconsistency #48527
Comments
Suppose you have tow sockets handled by two asynchat.async_chat class class1(asynchat.async_chat): ... def mymethod(self): Since push_with_producer automatically calls initiate_send() if an error The patch in attachment does that. |
The idea is good, but seems that error handling should be inlined into initiate_send. Also those 3 special exceptions should be defined once in the module instead of repeating them. |
This issue is 6 years old. I don't understand the bug and the patch has no unit test. I suggest to close the issue as out of date. The asynchat module is now deprecated in favor of the new shiny asyncio module. |
asynchat has been deprecated for a long time, it's unlikely we will do anything with it now. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: