➜

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 gvanrossum
Recipients asvetlov, brett.cannon, docs@python, ezio.melotti, giampaolo.rodola, gvanrossum, pitrou, vstinner, yselivanov
Date 2015-10-29.20:12:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446149548.48.0.382565913351.issue25501@psf.upfronthosting.co.za>
In-reply-to
Content 
Honestly I think it's better if most people keep using coroutine/yield-from instead of async/await for a few more releases; their code will be more portable, since it takes forever to update old datacenters. We put in async/await with an eye towards the future. But we're keeping yield-from around for a long time too. And that's also why we support asyncio for 3.3.
History
Date User Action Args
2015-10-29 20:12:28gvanrossumsetrecipients: + gvanrossum, brett.cannon, pitrou, vstinner, giampaolo.rodola, ezio.melotti, asvetlov, docs@python, yselivanov
2015-10-29 20:12:28gvanrossumsetmessageid: <1446149548.48.0.382565913351.issue25501@psf.upfronthosting.co.za>
2015-10-29 20:12:28gvanrossumlinkissue25501 messages
2015-10-29 20:12:28gvanrossumcreate