[Python-Dev] test_multiprocessing:test_listener_client flakiness (original) (raw)

Jesse Noller jnoller at gmail.com
Wed Jun 18 19:55:12 CEST 2008

On Wed, Jun 18, 2008 at 1:51 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:

Amaury Forgeot d'Arc <amauryfa gmail.com> writes:

OK, I am not a tcp expert. How about the following patch? It seems to me that it is wrong for the server to lie about the address it listens to. Maybe I'm missing something but... if the client part defaults to connecting to "localhost" in TCP mode, why doesn't the server part also default to listening on "localhost" in TCP mode? Having different address detection algorithms on both ends sounds like a recipe for bugs like this. In any case, perhaps one should ask guidance to the original author before making important changes like this one.

The server component is listening to localhost by default. The client in the code I pasted has the server's .address attribute passed into it to tell the client where to connect to.

-jesse

More information about the Python-Dev mailing list