This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: The get_event_loop change in bpo28613 did not update the documentation
Type: behavior Stage: resolved
Components: Demos and Tools Versions: Python 3.8, Python 3.7, Python 3.6
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: r.david.murray, yselivanov
Priority: normal Keywords: patch

Created on 2017-11-22 18:28 by r.david.murray, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 4510 merged pablogsal, 2017-11-23 00:08
Messages (2)
msg306744 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2017-11-22 18:28
No changes were made to the documentation of get_event_loop when its behavior was modified to return the loop running the future/coroutine when called from that context.  The documentation still says it gets the loop associated with the thread unconditionally.
msg307964 - (view) Author: Yury Selivanov (yselivanov) * (Python committer) Date: 2017-12-10 17:35
New changeset 77106b2c21e59d0466742cc3afa50f9e8345e186 by Yury Selivanov (Pablo Galindo) in branch 'master':
bpo-32114: Updated the documentation for get_event_loop to reflect the policy change (#4510)
Date User Action Args
2022-04-11 14:58:54adminsetgithub: 76295
2017-12-10 17:35:19yselivanovsetstatus: open -> closed
resolution: fixed
stage: patch review -> resolved
2017-12-10 17:35:01yselivanovsetmessages: + msg307964
2017-11-23 00:08:57pablogsalsetkeywords: + patch
stage: needs patch -> patch review
pull_requests: + pull_request4447
2017-11-22 18:28:35r.david.murraycreate