Movatterモバイル変換


[0]ホーム

URL:


homepage

Issue39381

This issue trackerhas been migrated toGitHub, and is currentlyread-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title:Fix get_event_loop documentation
Type:Stage:resolved
Components:asyncioVersions:Python 3.9, Python 3.8, Python 3.7
process
Status:closedResolution:fixed
Dependencies:Superseder:
Assigned To:Nosy List: asvetlov, yselivanov
Priority:normalKeywords:patch

Created on2020-01-18 13:30 byasvetlov, last changed2022-04-11 14:59 byadmin. This issue is nowclosed.

Pull Requests
URLStatusLinkedEdit
PR 18051mergedasvetlov,2020-01-18 13:39
PR 18084mergedmiss-islington,2020-01-20 22:48
PR 18085mergedmiss-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."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
DateUserActionArgs
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
Supported byThe Python Software Foundation,
Powered byRoundup
Copyright © 1990-2022,Python Software Foundation
Legal Statements

[8]ページ先頭

©2009-2025 Movatter.jp