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
Contributor

@miss-islington miss-islington 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

…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>
@miss-islington
Copy link
Contributor Author

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

@miss-islington miss-islington merged commit bb8fc8b into python:3.8 Sep 10, 2019
@miss-islington miss-islington deleted the backport-537877d-3.8 branch September 10, 2019 11:26
@miss-islington
Copy link
Contributor Author

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

1 similar comment
@miss-islington
Copy link
Contributor Author

@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
Development

Successfully merging this pull request may close these issues.

5 participants