-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-40782: Change asyncio.AbstractEventLoop.run_in_executor to be a method not a coroutine #21852
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
Conversation
asyncio.AbstractEventLoop.run_in_executor should be a method that returns an asyncio Future, not an async method. This matches the concrete implementations, and the documentation better.
This comment has been minimized.
This comment has been minimized.
Thanks, be sure to check yourself per instructions of the CLA bot in a few business days. |
@gvanrossum already done. |
Thanks @jamesba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
Thanks @jamesba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9. |
GH-21903 is a backport of this pull request to the 3.8 branch. |
…ethod not a coroutine (pythonGH-21852) asyncio.AbstractEventLoop.run_in_executor should be a method that returns an asyncio Future, not an async method. This matches the concrete implementations, and the documentation better. (cherry picked from commit 29f8429) Co-authored-by: James Weaver <james.barrett@bbc.co.uk>
GH-21904 is a backport of this pull request to the 3.9 branch. |
…ethod not a coroutine (pythonGH-21852) asyncio.AbstractEventLoop.run_in_executor should be a method that returns an asyncio Future, not an async method. This matches the concrete implementations, and the documentation better. (cherry picked from commit 29f8429) Co-authored-by: James Weaver <james.barrett@bbc.co.uk>
…ethod not a coroutine (GH-21852) asyncio.AbstractEventLoop.run_in_executor should be a method that returns an asyncio Future, not an async method. This matches the concrete implementations, and the documentation better. (cherry picked from commit 29f8429) Co-authored-by: James Weaver <james.barrett@bbc.co.uk>
…ethod not a coroutine (GH-21852) asyncio.AbstractEventLoop.run_in_executor should be a method that returns an asyncio Future, not an async method. This matches the concrete implementations, and the documentation better. (cherry picked from commit 29f8429) Co-authored-by: James Weaver <james.barrett@bbc.co.uk>
|
|
…ethod not a coroutine (pythonGH-21852) asyncio.AbstractEventLoop.run_in_executor should be a method that returns an asyncio Future, not an async method. This matches the concrete implementations, and the documentation better.
…ethod not a coroutine (pythonGH-21852) asyncio.AbstractEventLoop.run_in_executor should be a method that returns an asyncio Future, not an async method. This matches the concrete implementations, and the documentation better.
asyncio.AbstractEventLoop.run_in_executor should be a method that returns an asyncio Future, not an async method.
This matches the concrete implementations, and the documentation better.
https://bugs.python.org/issue40782
Automerge-Triggered-By: @gvanrossum