Andrew Svetlov <andrew.svet...@gmail.com> added the comment:
No. pause_writing/resume_writing are protocol callbacks called by transport. User code should respond to these callbacks by stopping sending data to transport (transport.write()). The logic is a little complicated but it is ok for very low-level asyncio API. Convenient user-facing wrappers like asyncio streams hide this logic by providing high-level primitives that support flow-control out of the box I'm closing the issue, nothing to do here on asyncio low-level side. ---------- resolution: -> not a bug _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue36981> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
