[issue34993] asyncio.streams.FlowControlMixin should be part of the API

Andrew Svetlov added the comment: #36889 deprecates using FlowXontrolMixin outside of asyncio -- ___ Python tracker ___ ___ Python-

[issue34993] asyncio.streams.FlowControlMixin should be part of the API

Andrew Svetlov added the comment: FlowControlMixing is a private API class. The class is not intended for the usage outside of asyncio. If you found it useful for you please feel free to copy-paste the class from asyncio sources into your project. The reason is: we want to keep freedom for ch

[issue34993] asyncio.streams.FlowControlMixin should be part of the API

Andrew Svetlov added the comment: 1. Trio has *stappled* streams for the case, especially useful for starting TLS session over stdin/stdout. We can master something too. 2. FlowControlMixin was always considered a **private** API. Would be nice to add an underscore prefix to the name if not t

[issue34993] asyncio.streams.FlowControlMixin should be part of the API

Yury Selivanov added the comment: asvetlov: need to handle this usecase with the new API; -1 on exposing FlowControlMixin though. -- ___ Python tracker ___ __

[issue34993] asyncio.streams.FlowControlMixin should be part of the API

New submission from xitop : This issue report is based on a SO question "How to create asyncio stream reader/writer for stdin/stdout?", its answer and comments. Link: https://stackoverflow.com/q/52089869/5378816 The key point is that two unidirectional pipes should be used the same way as on