This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author j1m
Recipients gvanrossum, j1m, socketpair, vstinner, yselivanov
Date 2016-06-29.16:21:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Guido, are you saying that the script runs without hanging for you?
(If you get a boatload of tracebacks, that's due to another asyncio bug in error handling.)

Are you running the version with prints?

This is an adaptation of the echo server and client from the docs.

The server runs in a thread.  It just echos it's input.

The client just waits for a message from the server, and then send messages (one in attached and waits for replies. When I run this on Mac and ubuntu 14.04, the server never sees the messages sent by the client.

I'm uploading a newer version that simplifies the messages data structure and adds some prints to, I think, make the sequence easier to see.

Fixing the bug that causes all the tracebacks to be printed would also make this easier to interpret.

Commenting out the code that makes and closes the socket connections with SO_LINGER and running should also make it easy to see the trivial expected client/server interaction.

I don't think the details of the interaction between the server and the client are very important, other than the fact that the client gets the first message from the server and the server doesn't get the subsequent message from the client.
Date User Action Args
2016-06-29 16:21:29j1msetrecipients: + j1m, gvanrossum, vstinner, socketpair, yselivanov
2016-06-29 16:21:29j1msetmessageid: <>
2016-06-29 16:21:29j1mlinkissue27386 messages
2016-06-29 16:21:28j1mcreate