You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2023. It is now read-only.
I don't understand the reasoning behind having two method. Can someone explain or at least point out where I can read about this design choice?
Why don't we have just one async method close which can be scheduled with asycnio.create_task or awaited in place if user whats to be sure that connections are closed?
The text was updated successfully, but these errors were encountered:
vanyakosmos
changed the title
[question] why you are using close and wait_close instead of just othe method?
[question] why you are using close and wait_close instead of just one method?
Feb 22, 2020
.close() will close the connection eventually so you don't need to call wait_close unless you don't want to proceed until the connection is actually closed.
Also note that wait_close was a new addition to that class in Python 3.7
I don't understand the reasoning behind having two method. Can someone explain or at least point out where I can read about this design choice?
Why don't we have just one async method
close
which can be scheduled withasycnio.create_task
or awaited in place if user whats to be sure that connections are closed?The text was updated successfully, but these errors were encountered: