[issue24487] Change asyncio.async() → ensure_future()

Changes by Yury Selivanov : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue24487] Change asyncio.async() → ensure_future()

Yury Selivanov added the comment: Thanks, Martin! -- resolution: out of date -> fixed ___ Python tracker ___ ___ Python-bugs-list mail

[issue24487] Change asyncio.async() → ensure_future()

Roundup Robot added the comment: New changeset 1b3be273e327 by Yury Selivanov in branch '3.5': Issue #24487: Rename async() -> ensure_future() in asyncio docs. https://hg.python.org/cpython/rev/1b3be273e327 New changeset 3dc2a113e8a7 by Yury Selivanov in branch 'default': Merge 3.5 (Issue #24487

[issue24487] Change asyncio.async() → ensure_future()

Martin Panter added the comment: Reopening. The patch still applies to the current code (e.g. revision df310e5ac015, 30 June). It changes eight references of “async()” that still exist in this revision. -- status: closed -> open ___ Python tracker

[issue24487] Change asyncio.async() → ensure_future()

Martin Panter added the comment: There are a few references left in that revision. For instance still suggests scheduling a coroutine by calling async(). But depending on the context this may cause a syntax error in 3.5, so I t

[issue24487] Change asyncio.async() → ensure_future()

Changes by Zachary Ware : -- resolution: not a bug -> out of date stage: patch review -> resolved ___ Python tracker ___ ___ Python-bu

[issue24487] Change asyncio.async() → ensure_future()

Yury Selivanov added the comment: Martin, I believe this was done as part of issue24180, see this commit https://hg.python.org/cpython/rev/9d9e445d25dc -- resolution: -> not a bug status: open -> closed ___ Python tracker

[issue24487] Change asyncio.async() → ensure_future()

New submission from Martin Panter: The async() function is marked as deprecated in 3.4.4. This patch replaces most references to it with references to ensure_future(). The exception is , which suggest