This issue trackerhas been migrated toGitHub, and is currentlyread-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.
Created on2020-01-18 13:30 byasvetlov, last changed2022-04-11 14:59 byadmin. This issue is nowclosed.
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)*![]() | 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."https://docs.python.org/3.7/library/asyncio-eventloop.html#asyncio.get_event_loopThis is not correct, a new loop is created implicitly only for the main thread, all other threads require set_event_loop() call |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:59:25 | admin | set | github: 83562 |
2020-01-20 22:52:57 | asvetlov | set | status: open -> closed resolution: fixed stage: patch review -> resolved |
2020-01-20 22:48:37 | miss-islington | set | pull_requests: +pull_request17477 |
2020-01-20 22:48:02 | miss-islington | set | pull_requests: +pull_request17476 |
2020-01-18 13:39:59 | asvetlov | set | keywords: +patch stage: patch review pull_requests: +pull_request17446 |
2020-01-18 13:30:41 | asvetlov | create |