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

aio: drain write buffer during send #2

Merged
merged 2 commits into from Dec 24, 2019
Merged

aio: drain write buffer during send #2

merged 2 commits into from Dec 24, 2019

Conversation

jsbronder
Copy link
Owner

Wait for the event loop write buffer to be drained when sending data.
This diverges from current asyncio APIs but they appear to be moving in
the same direction, https://bugs.python.org/issue38242

Fixes #1

Wait for the event loop write buffer to be drained when sending data.
This diverges from current asyncio APIs but they appear to be moving in
the same direction, https://bugs.python.org/issue38242

Fixes #1
Per upstream, the documentation hinting that this was harmless and
desirable was misleading.  For most applications we likely do not
want this behavior so disable it in the bind() wrapper.

https://bugs.python.org/issue37228
@jsbronder jsbronder merged commit e847957 into master Dec 24, 2019
@jsbronder jsbronder deleted the next branch December 24, 2019 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DatagramStream.send should respect flow control
2 participants