Martin Panter added the comment: There are a few references left in that revision. For instance <https://docs.python.org/3.5/library/asyncio-task.html#coroutines> still suggests scheduling a coroutine by calling async(). But depending on the context this may cause a syntax error in 3.5, so I think it should suggest calling ensure_future() instead.
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24487> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
