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: Fix get_event_loop documentation
Type: Stage: resolved
Components: asyncio Versions: Python 3.9, Python 3.8, Python 3.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: asvetlov, yselivanov
Priority: normal Keywords: patch

Created on 2020-01-18 13:30 by asvetlov, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 18051 merged asvetlov, 2020-01-18 13:39
PR 18084 merged miss-islington, 2020-01-20 22:48
PR 18085 merged miss-islington, 2020-01-20 22:48
Messages (1)
msg360244 - (view) Author: Andrew Svetlov (asvetlov) * (Python committer) Date: 2020-01-18 13:30
The current documentation says: "If there is no current event loop set in the current OS thread and set_event_loop() has not yet been called, asyncio will create a new event loop and set it as the current one."

This is not correct, a new loop is created implicitly only for the main thread, all other threads require set_event_loop() call
Date User Action Args
2022-04-11 14:59:25adminsetgithub: 83562
2020-01-20 22:52:57asvetlovsetstatus: open -> closed
resolution: fixed
stage: patch review -> resolved
2020-01-20 22:48:37miss-islingtonsetpull_requests: + pull_request17477
2020-01-20 22:48:02miss-islingtonsetpull_requests: + pull_request17476
2020-01-18 13:39:59asvetlovsetkeywords: + patch
stage: patch review
pull_requests: + pull_request17446
2020-01-18 13:30:41asvetlovcreate