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.

Author asvetlov
Recipients asvetlov, yselivanov
Date 2020-01-18.13:30:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579354241.45.0.104349162739.issue39381@roundup.psfhosted.org>
In-reply-to
Content
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_loop

This 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
2020-01-18 13:30:41asvetlovsetrecipients: + asvetlov, yselivanov
2020-01-18 13:30:41asvetlovsetmessageid: <1579354241.45.0.104349162739.issue39381@roundup.psfhosted.org>
2020-01-18 13:30:41asvetlovlinkissue39381 messages
2020-01-18 13:30:41asvetlovcreate