classification
Title: document the new behavior of get_event_loop() in Python 3.6
Type: Stage: needs patch
Components: asyncio, Documentation Versions: Python 3.7, Python 3.6
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: chris.jerdonek, docs@python, yselivanov
Priority: normal Keywords:

Created on 2017-07-15 02:03 by chris.jerdonek, last changed 2017-07-16 07:49 by daxlab.

Pull Requests
URL Status Linked Edit
PR 2731 open daxlab, 2017-07-16 07:49
Messages (1)
msg298380 - (view) Author: Chris Jerdonek (chris.jerdonek) * (Python committer) Date: 2017-07-15 02:03
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.
History
Date User Action Args
2017-07-16 07:49:04daxlabsetpull_requests: + pull_request2791
2017-07-15 04:45:55Mariattasetstage: needs patch
versions: + Python 3.7
2017-07-15 02:11:44chris.jerdoneksetnosy: + yselivanov
components: + asyncio
2017-07-15 02:10:34chris.jerdoneksettitle: document the new behavior of get_event_loop() Python 3.6 -> document the new behavior of get_event_loop() in Python 3.6
2017-07-15 02:03:41chris.jerdonekcreate