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 martin.panter
Recipients docs@python, martin.panter, ncoghlan, yselivanov
Date 2015-06-22.12:00:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1434974436.12.0.0473100135758.issue24439@psf.upfronthosting.co.za>
In-reply-to
Content
When I update my patch I can try updating the asyncio section. However I have only had limited experience with asyncio, so feel free to suggest things to add. Here is a list of things I think may need changing:

* “async def” routines are allowed in addition to generators in asyncio (e.g. in Task constructor)
* Other awaitables are also accepted as asyncio coroutines
* List of “yield from” actions could be augmented with “await”, “async for”, etc
* The coroutines provided by asyncio are both iterable and awaitable, so they may be used with both “yield from” and “await”
* Change references of asyncio.async() to ensure_future()
History
Date User Action Args
2015-06-22 12:00:36martin.pantersetrecipients: + martin.panter, ncoghlan, docs@python, yselivanov
2015-06-22 12:00:36martin.pantersetmessageid: <1434974436.12.0.0473100135758.issue24439@psf.upfronthosting.co.za>
2015-06-22 12:00:36martin.panterlinkissue24439 messages
2015-06-22 12:00:36martin.pantercreate