Charles-François Natali <neolo...@free.fr> added the comment: > I explain a reliable method to reproduce this issue on Linux
It's a way to reproduce the symptom (i.e. connection refused because you're trying to connect to 127.0.0.2 while the server is listening on 127.0.0.1), but not the cause: if the server binds to 'localhost' and the client connects to 'localhost', it should work. But like you, I think it could be a good idea to change support.HOST to 127.0.0.1, to rule out name resolution delay (especially since Windows 7 doens't use its host file to resolve 'localhost' anymore, but calls the DNS solver). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11812> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
