diff options
| -rw-r--r-- | Doc/library/asyncio-eventloops.rst | 5 | ||||
| -rw-r--r-- | Doc/whatsnew/3.6.rst | 2 |
2 files changed, 5 insertions, 2 deletions
diff --git a/Doc/library/asyncio-eventloops.rst b/Doc/library/asyncio-eventloops.rst index 3051fde..7f6e953 100644 --- a/Doc/library/asyncio-eventloops.rst +++ b/Doc/library/asyncio-eventloops.rst @@ -176,12 +176,15 @@ An event loop policy must implement the following interface: Get the event loop for the current context. Returns an event loop object implementing the :class:`AbstractEventLoop` - interface. + interface. In case called from coroutine, it returns the currently + running event loop. Raises an exception in case no event loop has been set for the current context and the current policy does not specify to create one. It must never return ``None``. + .. versionchanged:: 3.6 + .. method:: set_event_loop(loop) Set the event loop for the current context to *loop*. diff --git a/Doc/whatsnew/3.6.rst b/Doc/whatsnew/3.6.rst index c4b6395..cb8c53a 100644 --- a/Doc/whatsnew/3.6.rst +++ b/Doc/whatsnew/3.6.rst @@ -819,7 +819,7 @@ Notable changes in the :mod:`asyncio` module since Python 3.5.0 (all backported to 3.5.x due to the provisional status): * The :func:`~asyncio.get_event_loop` function has been changed to - always return the currently running loop when called from couroutines + always return the currently running loop when called from coroutines and callbacks. (Contributed by Yury Selivanov in :issue:`28613`.) |