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 yselivanov
Recipients asvetlov, tontinton, yselivanov
Date 2020-07-15.23:25:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1594855503.19.0.209609552026.issue41305@roundup.psfhosted.org>
In-reply-to
Content
> Im interested in learning about the new api.

There are two problems with the current API:

1. Reader and writer are separate objects, while they should be one.
2. Writer.write is not a coroutine, although it should be one.

There are other minor nits, but that's the crux of the problem. So we need a new streams design + a new set of APIs to work with it (and streams are in many places, like in the subprocess APIs).

Trio was going to stabilize their own streaming API and we thought it would be great if our new API was compatible with it (not sure if they did stabilize it or not).

I was going to lead the project myself (and still am) but dropped the ball and we missed 3.9 to do this. If you want to start working on this I'd be glad to assist with discussions & reviews.
History
Date User Action Args
2020-07-15 23:25:03yselivanovsetrecipients: + yselivanov, asvetlov, tontinton
2020-07-15 23:25:03yselivanovsetmessageid: <1594855503.19.0.209609552026.issue41305@roundup.psfhosted.org>
2020-07-15 23:25:03yselivanovlinkissue41305 messages
2020-07-15 23:25:03yselivanovcreate