From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Thu, 5 May 2022 00:36:04 +0000 (-0700) Subject: gh-92223: Remove pre-Python 3.7 alternative in asyncio docs (GH-92224) X-Git-Tag: v3.9.13~40 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d82a769a1ded6dfa702800c83a68d051299b01fc;p=thirdparty%2FPython%2Fcpython.git gh-92223: Remove pre-Python 3.7 alternative in asyncio docs (GH-92224) (cherry picked from commit d1b2e989be2bc5128d6602e4f370d0ee6f5ac476) Co-authored-by: Sebastian Rittau --- diff --git a/Doc/library/asyncio-task.rst b/Doc/library/asyncio-task.rst index 38b12e44b6de..7c12e2eda1c4 100644 --- a/Doc/library/asyncio-task.rst +++ b/Doc/library/asyncio-task.rst @@ -20,7 +20,7 @@ Coroutines :term:`Coroutines ` declared with the async/await syntax is the preferred way of writing asyncio applications. For example, the following -snippet of code (requires Python 3.7+) prints "hello", waits 1 second, +snippet of code prints "hello", waits 1 second, and then prints "world":: >>> import asyncio @@ -259,21 +259,6 @@ Creating Tasks :exc:`RuntimeError` is raised if there is no running loop in current thread. - This function has been **added in Python 3.7**. Prior to - Python 3.7, the low-level :func:`asyncio.ensure_future` function - can be used instead:: - - async def coro(): - ... - - # In Python 3.7+ - task = asyncio.create_task(coro()) - ... - - # This works in all Python versions but is less readable - task = asyncio.ensure_future(coro()) - ... - .. important:: Save a reference to the result of this function, to avoid