Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-39381: Fix asyncio.get_event_loop() documentation #18051

Merged
merged 1 commit into from Jan 20, 2020

Conversation

@asvetlov
Copy link
Contributor

asvetlov commented Jan 18, 2020

Mention that the function implicitly creates a new event loop only if called from the main thread.

https://bugs.python.org/issue39381

Mention that the function implicitly creates new event loop only if called from the main thread.
@1st1
1st1 approved these changes Jan 20, 2020
@asvetlov asvetlov merged commit 2c49bec into python:master Jan 20, 2020
5 checks passed
5 checks passed
Docs
Details
Azure Pipelines PR #20200118.30 succeeded
Details
bedevere/issue-number Issue number 39381 found
Details
bedevere/news News entry found in Misc/NEWS.d
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@asvetlov asvetlov deleted the asvetlov:fix-get_event_loop-docs branch Jan 20, 2020
@miss-islington

This comment has been minimized.

Copy link

miss-islington commented Jan 20, 2020

Thanks @asvetlov for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8.
🐍🍒🤖 I'm not a witch! I'm not a witch!

miss-islington added a commit to miss-islington/cpython that referenced this pull request Jan 20, 2020
Mention that the function implicitly creates new event loop only if called from the main thread.
(cherry picked from commit 2c49bec)

Co-authored-by: Andrew Svetlov <andrew.svetlov@gmail.com>
@bedevere-bot

This comment has been minimized.

Copy link

bedevere-bot commented Jan 20, 2020

GH-18084 is a backport of this pull request to the 3.8 branch.

miss-islington added a commit to miss-islington/cpython that referenced this pull request Jan 20, 2020
Mention that the function implicitly creates new event loop only if called from the main thread.
(cherry picked from commit 2c49bec)

Co-authored-by: Andrew Svetlov <andrew.svetlov@gmail.com>
@bedevere-bot

This comment has been minimized.

Copy link

bedevere-bot commented Jan 20, 2020

GH-18085 is a backport of this pull request to the 3.7 branch.

miss-islington added a commit that referenced this pull request Jan 20, 2020
Mention that the function implicitly creates new event loop only if called from the main thread.
(cherry picked from commit 2c49bec)

Co-authored-by: Andrew Svetlov <andrew.svetlov@gmail.com>
miss-islington added a commit that referenced this pull request Jan 20, 2020
Mention that the function implicitly creates new event loop only if called from the main thread.
(cherry picked from commit 2c49bec)

Co-authored-by: Andrew Svetlov <andrew.svetlov@gmail.com>
petdance added a commit to petdance/cpython that referenced this pull request Jan 21, 2020
Mention that the function implicitly creates new event loop only if called from the main thread.
petdance added a commit to petdance/cpython that referenced this pull request Jan 21, 2020
Mention that the function implicitly creates new event loop only if called from the main thread.
petdance added a commit to petdance/cpython that referenced this pull request Jan 21, 2020
Mention that the function implicitly creates new event loop only if called from the main thread.
petdance added a commit to petdance/cpython that referenced this pull request Jan 21, 2020
Mention that the function implicitly creates new event loop only if called from the main thread.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.