traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix asyncio.get_event_loop() documentation (GH-18051) 

Mention that the function implicitly creates new event loop only if called from the main thread.
(cherry picked from commit 2c49becc69)

Co-authored-by: Andrew Svetlov <andrew.svetlov@gmail.com>
This commit is contained in:
Miss Islington (bot) 2020-01-20 14:51:57 -08:00 committed by GitHub
parent a360070121
commit 2469066a4b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Doc/library/asyncio-eventloop.rst
View File

@ -34,8 +34,10 @@ an event loop:
.. function:: get_event_loop() .. function:: get_event_loop()
Get the current event loop. If there is no current event loop set Get the current event loop.
in the current OS thread and :func:`set_event_loop` has not yet
If there is no current event loop set in the current OS thread,
the OS thread is main, and :func:`set_event_loop` has not yet
been called, asyncio will create a new event loop and set it as the been called, asyncio will create a new event loop and set it as the
current one. current one.

2
Misc/NEWS.d/next/Documentation/2020-01-18-15-37-56.bpo-39381.wTWe8d.rst Normal file
View File

@ -0,0 +1,2 @@
Mention in docs that :func:`asyncio.get_event_loop` implicitly creates new
event loop only if called from the main thread.