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

[3.8] bpo-36373: Deprecate explicit loop parameter in all public asyncio APIs [locks] (GH-13920) #15835

Merged
merged 1 commit into from Sep 10, 2019

Conversation

@miss-islington
Copy link

commented Sep 10, 2019

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

https://bugs.python.org/issue36373

bpo-36373: Deprecate explicit loop parameter in all public asyncio AP…
…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>
@miss-islington

This comment has been minimized.

Copy link
Author

commented Sep 10, 2019

@eamanu: Status check is done, and it's a success .

@miss-islington miss-islington merged commit bb8fc8b into python:3.8 Sep 10, 2019

6 checks passed

Azure Pipelines PR #20190910.38 succeeded
Details
bedevere/issue-number Issue number 36373 found
Details
bedevere/maintenance-branch-pr Valid maintenance branch PR title.
bedevere/news "skip news" label found
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@miss-islington miss-islington deleted the miss-islington:backport-537877d-3.8 branch Sep 10, 2019

@miss-islington

This comment has been minimized.

Copy link
Author

commented Sep 10, 2019

@eamanu: Status check is done, and it's a success .

1 similar comment
@miss-islington

This comment has been minimized.

Copy link
Author

commented Sep 10, 2019

@eamanu: Status check is done, and it's a success .

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.