This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Paulo Costa, gvanrossum, martin.panter, vstinner, yselivanov
Date 2016-03-17.14:57:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458226635.69.0.873800282494.issue26270@psf.upfronthosting.co.za>
In-reply-to
Content
> Anyway, despite the existence of streams and protocols, I still believe that `asyncio.read()`, `asyncio.write()` and `asyncio.select()` would be nice-to-have low-level APIs.

You can probably develop your own helper functions based on existing asyncio function.

I'm opposed to add such helper functions since it doesn't fit into the design of asyncio. Please read a little bit more about event loops and how asyncio is design. Don't hesitate to come back if you have something concrete, but IMHO this discussion should be moved to the python-tulip Google Groups rather than a *bug tracker*.

I close the issue.
History
Date User Action Args
2016-03-17 14:57:15vstinnersetrecipients: + vstinner, gvanrossum, martin.panter, yselivanov, Paulo Costa
2016-03-17 14:57:15vstinnersetmessageid: <1458226635.69.0.873800282494.issue26270@psf.upfronthosting.co.za>
2016-03-17 14:57:15vstinnerlinkissue26270 messages
2016-03-17 14:57:15vstinnercreate