Message 307375 - 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, yselivanov
Date	2017-12-01.09:44:32
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
As discussed several times before we need to convert `@coroutine` / `yield from` to async/await. All existing functionality should keep working (like yielding from new style coroutine and `with (yield from lock)`. We could deprecate the later though. The change should be huge but there is no alternative, keeping `yield from` in stdlib looks uglier and uglier every year. Unittests should be changed as well (keeping several `yield from` for checking backward compatibility is Ok). Opinions?

As discussed several times before we need to convert `@coroutine` / `yield from` to async/await.

All existing functionality should keep working (like yielding from new style coroutine and `with (yield from lock)`.

We could deprecate the later though.

The change should be huge but there is no alternative, keeping `yield from` in stdlib looks uglier and uglier every year.

Unittests should be changed as well (keeping several `yield from` for checking backward compatibility is Ok).


Opinions?

History
Date	User	Action	Args
2017-12-01 09:44:32	asvetlov	set	recipients: + asvetlov, yselivanov
2017-12-01 09:44:32	asvetlov	set	messageid: <[email protected]>
2017-12-01 09:44:32	asvetlov	link	issue32193 messages
2017-12-01 09:44:32	asvetlov	create