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 aeros, asvetlov, njs, tontinton, yselivanov
Date 2020-07-16.19:49:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1594928952.68.0.817598858439.issue41305@roundup.psfhosted.org>
In-reply-to
Content
> Is it simply combining stream reader and stream writer into a single object and changing the write() function to always wait the write (thus deprecating drain) and that's it?

Pretty much. We might also rename a few APIs here and there, like "close()" should become an "async def aclose()"

We also will likely want to define a few ABCs.

Which brings me to the most important point: what we need it not coding it (yet), but rather drafting the actual proposal and posting it to https://discuss.python.org/c/async-sig/20.  Once a formal proposal is there we can proceed with the implementation.

It's a bit of a process to follow, but we have to do it this way.
History
Date User Action Args
2020-07-16 19:49:12yselivanovsetrecipients: + yselivanov, njs, asvetlov, aeros, tontinton
2020-07-16 19:49:12yselivanovsetmessageid: <1594928952.68.0.817598858439.issue41305@roundup.psfhosted.org>
2020-07-16 19:49:12yselivanovlinkissue41305 messages
2020-07-16 19:49:12yselivanovcreate