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.