[issue25501] Use async/await through asyncio docs

Changes by Brett Cannon : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue25501] Use async/await through asyncio docs

Guido van Rossum added the comment: 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 futu

[issue25501] Use async/await through asyncio docs

Brett Cannon added the comment: Once 3.4.4 launches the need to keep the docs synced with a version that doesn't support async/await goes away. And worrying about 3.3 isn't necessary since asyncio was added in 3.4. So once 3.4.4 is released and we close the 3.4 branch to bugfixes can we update

[issue25501] Use async/await through asyncio docs

Andrew Svetlov added the comment: We have dropped 3.3 in aiohttp BTW. Proper handling of resource leaks is too annoying without PEP 442 which don't crash with core dump starting from Python 3.4.1 -- ___ Python tracker

[issue25501] Use async/await through asyncio docs

Andrew Svetlov added the comment: Also sphinx (pygments actually) still do not support async/await syntax highlighting yet. -- nosy: +asvetlov ___ Python tracker ___ ___

[issue25501] Use async/await through asyncio docs

Guido van Rossum added the comment: It makes it more awkward to keep the asyncio docs in sync between 3.4 and 3.5. Also it makes copying examples harder for users who need compatibility with 3.4 or 3.3. -- ___ Python tracker

[issue25501] Use async/await through asyncio docs

Changes by Ezio Melotti : -- keywords: +easy nosy: +ezio.melotti type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mai

[issue25501] Use async/await through asyncio docs

New submission from Brett Cannon: The asyncio docs still use `yield from` and @asyncio.coroutine all over the place instead of async/await. It would be best to update the docs to follow best practices (unless there is some reason I can't think of as to why this hasn't happened yet). -