bpo-32114: Updated the documentation for get_event_loop to reflect the policy change#4510
Merged
Conversation
pablogsal
changed the title
merwok
reviewed
Nov 24, 2017
| happens when :meth:`~AbstractEventLoopPolicy.get_event_loop` is called from a | ||
| running future/coroutine, in which case it will return the current loop | ||
| running that future/coroutine. | ||
| If the current thread doesn't already have an event loop associated with it, |
Member
There was a problem hiding this comment.
Add an empty line before this to make a new paragraph.
Member
Author
|
@1st1 Can you check that these changes to the documentation are correct? |
1st1
approved these changes
Dec 10, 2017
Member
|
Merged. Thanks for the PR! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://bugs.python.org/issue32114