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
asyncio: Document that TCP_NODELAY is now used by default #72276
Comments
This is marked as a release blocker but, since it's just a doc change, I'm not going to hold 3.6.0 for it. It would be nice to get it in, though. |
Yury: I don't understand your issue, can you please elaborate? Do you mean that the default value of the TCP_NODELAY changed in Python 3.6? Otherwise, why do you consider it as a release blocker? The Python 3.6 release must be blocked by a TCP flag? Really? |
The change is that TCP_NODELAY option is set by default in 3.6. It was not the case in 3.5. |
Ah, it's a change in _asyncio_, ok. I missed that from the issue title, so I changed the title. |
I added the following to Doc/library/asyncio-protocol.rst .. versionchanged:: 3.6.0 Let me know if this patch works. |
+.. versionchanged:: 3.6.0 3.6.0 -> 3.6 + The socket option TCP_NODELAY is now set by default. TCP_NODELAY -> |
Thanks, Berker :) |
New changeset 726308cfe3b5 by Victor Stinner in branch '3.6': |
New changeset 150d36dbe3ba by Victor Stinner in branch '3.6': |
Yury, look good to you? |
New changeset 853e3f4d6cd9 by Yury Selivanov in branch '3.6': New changeset 0d209cc7ffdc by Yury Selivanov in branch 'default': |
Yes; committed the patch with a small addition. Thanks, Mariatta! |
New changeset dfd1019f75f9 by Yury Selivanov in branch '3.6': |
[cherrypicked for 3.6.0rc2] |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: