bpo-36373: Deprecate explicit loop parameter in all public asyncio APIs [locks]#13920
bpo-36373: Deprecate explicit loop parameter in all public asyncio APIs [locks]#13920miss-islington merged 5 commits into
Conversation
This PR deprecate explicit loop parameters in all public asyncio APIs This issues is split to be easier to review. Third step: locks.py
|
Please don't merge because |
Sorry, something went wrong.
|
@asvetlov I think this PR is ready now |
Sorry, something went wrong.
asvetlov
left a comment
There was a problem hiding this comment.
LGTM
Sorry for the delay.
Thank for your patience.
Sorry, something went wrong.
|
Thanks @eamanu for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
Sorry, something went wrong.
|
I'm having trouble backporting to |
Sorry, something went wrong.
|
Thanks @eamanu for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
Sorry, something went wrong.
…Is [locks] (pythonGH-13920) This PR deprecate explicit loop parameters in all public asyncio APIs This issues is split to be easier to review. Third step: locks.py https://bugs.python.org/issue36373 (cherry picked from commit 537877d) Co-authored-by: Emmanuel Arias <emmanuelarias30@gmail.com>
…Is [locks] (GH-13920) This PR deprecate explicit loop parameters in all public asyncio APIs This issues is split to be easier to review. Third step: locks.py https://bugs.python.org/issue36373 (cherry picked from commit 537877d) Co-authored-by: Emmanuel Arias <emmanuelarias30@gmail.com>
…PIs [locks] (pythonGH-13920) This PR deprecate explicit loop parameters in all public asyncio APIs This issues is split to be easier to review. Third step: locks.py https://bugs.python.org/issue36373
This PR deprecate explicit loop parameters in all public asyncio APIs
This issues is split to be easier to review.
Third step: locks.py
https://bugs.python.org/issue36373
Automerge-Triggered-By: @asvetlov