STINNER Victor <vstin...@redhat.com> added the comment:
> write.setsockopt(socket.SOL_SOCKET, socket.SO_SNDBUF, 0) Instead of that, I also tried: read.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, 1) write.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, 1) But I'm able to reproduce the bug with TCP_NODELAY=1 on the write end. (The option should have no impact on the read end, but I added it anyway, just in case, I still reproduce the bug.) MSDN documentation for TCP_NODELAY: "Disables the Nagle algorithm for send coalescing.This socket option is included for backward compatibility with Windows Sockets 1.1 " https://docs.microsoft.com/en-us/windows/desktop/api/winsock/nf-winsock-setsockopt ---------- nosy: +yselivanov _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34130> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
