Message 352931 - Python tracker

➜

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	asvetlov
Recipients	asvetlov, gvanrossum, lukasz.langa, njs, xtreak, yselivanov
Date	2019-09-21.08:07:35
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
There is an alternative proposal: let's deprecate and eventually remove streams API entirely (for sockets, pipes, and subprocesses). By this, we will never have a chance to conflict with trio. Another option is removing asyncio at all (again to never conflict with trio and possible future awesome libraries) but the ship has sailed maybe.

There is an alternative proposal: let's deprecate and eventually remove streams API entirely (for sockets, pipes, and subprocesses).
By this, we will never have a chance to conflict with trio.

Another option is removing asyncio at all (again to never conflict with trio and possible future awesome libraries) but the ship has sailed maybe.

History
Date	User	Action	Args
2019-09-21 08:07:35	asvetlov	set	recipients: + asvetlov, gvanrossum, njs, lukasz.langa, yselivanov, xtreak
2019-09-21 08:07:35	asvetlov	set	messageid: <[email protected]>
2019-09-21 08:07:35	asvetlov	link	issue38242 messages
2019-09-21 08:07:35	asvetlov	create