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 pitrou
Recipients giampaolo.rodola, neologix, pitrou
Date 2013-08-21.10:43:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <2126158028.2393321.1377081830484.JavaMail.root@zimbra10-e2.priv.proxad.net>
In-reply-to <CAH_1eM1Amj06aC4NqQTUwVJdDuaLzu4+yb3pz_33+=Xmx1S53w@mail.gmail.com>
Content
> Changing support.HOST from 'localhost' to '127.0.0.1' means that on
> dual-stack
> hosts (I don't think the test suite would run on IPv6-only hosts
> anyway), the
> tests will now always use IPv4, whereas they are currently using
> either IPv6 or
> IPv4 addresses depending on the host's name resolution settings.

That would only be true if the server we are contacting happens to
listen on both IPv6 and IPv4, right? I don't think we have such a
situation in the test suite. Clients can use create_connection()
for transparent support of IPv6 and IPv4, but servers have to choose
a family when creating their socket.
History
Date User Action Args
2013-08-21 10:43:57pitrousetrecipients: + pitrou, giampaolo.rodola, neologix
2013-08-21 10:43:57pitroulinkissue18792 messages
2013-08-21 10:43:57pitroucreate