bpo-36373: Deprecate explicit loop parameter in all public asyncio APIs [streams]#13671
bpo-36373: Deprecate explicit loop parameter in all public asyncio APIs [streams]#13671miss-islington merged 3 commits into
Conversation
This PR deprecate explicit loop parameters in all public asyncio APIs This issues is split to be easier to review. Second step: streams.py
asvetlov
left a comment
There was a problem hiding this comment.
Please remove all deprecations in public API but add these warnings to open_connection(), start_server(), open_unix_connection(), start_unix_server() instead.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
|
I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @asvetlov: please review the changes made to this pull request. |
Sorry, something went wrong.
asvetlov
left a comment
There was a problem hiding this comment.
Please run your PR by ./python -Weeror -m test -v test_asyncio.
I suspect that some tests will fail (but didn't check it myself).
These tests should be wrapped by with self.assertWarns(DeprecationWarning): ... construction
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
asvetlov
left a comment
There was a problem hiding this comment.
please drop the check here
Sorry, something went wrong.
|
I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @asvetlov: please review the changes made to this pull request. |
Sorry, something went wrong.
|
@asvetlov I run the |
Sorry, something went wrong.
|
Sorry, I can't merge this PR. Reason: |
Sorry, something went wrong.
|
Thanks @eamanu for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
Sorry, something went wrong.
|
Thank you @eamanu The next big target is asyncio documentation cleanup (plus I need to land multithreaded support back again). |
Sorry, something went wrong.
|
@eamanu would you take a look on |
Sorry, something went wrong.
…Is [streams] (GH-13671) This PR deprecate explicit loop parameters in all public asyncio APIs This issues is split to be easier to review. Second step: streams.py https://bugs.python.org/issue36373 (cherry picked from commit 6d64a8f) Co-authored-by: Emmanuel Arias <emmanuelarias30@gmail.com>
|
Thank you. No rush, we have enough time during betas |
Sorry, something went wrong.
…Is [streams] (pythonGH-13671) This PR deprecate explicit loop parameters in all public asyncio APIs This issues is split to be easier to review. Second step: streams.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.
Second step: streams.py
https://bugs.python.org/issue36373