[docs] [issue30935] document the new behavior of get_event_loop() Python 3.6
Chris Jerdonek
report at bugs.python.org
Fri Jul 14 22:03:41 EDT 2017
New submission from Chris Jerdonek:
Currently, the Python asyncio.get_event_loop() docs don't say that get_event_loop() returns the currently running event loop when it is called from a coroutine:
https://docs.python.org/3/library/asyncio-eventloops.html#asyncio.get_event_loop
https://docs.python.org/3/library/asyncio-eventloops.html#asyncio.AbstractEventLoopPolicy.get_event_loop
This is new behavior that was introduced in Python 3.6 in this issue:
https://github.com/python/asyncio/pull/452
Without this, the docs make it seem like get_event_loop() should return the loop that was last passed to set_event_loop().
This could be added with a "Changed in version 3.6" note.
----------
assignee: docs at python
components: Documentation
messages: 298380
nosy: chris.jerdonek, docs at python
priority: normal
severity: normal
status: open
title: document the new behavior of get_event_loop() Python 3.6
versions: Python 3.6
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30935>
_______________________________________
More information about the docs
mailing list