Message6359

Alex, it solves the bug by enabling creation of IPV6 sockets. That creates a new problem for the WinXP users with crappy ipv6 support: they'll eventually trigger a Java nio error about ipv6 not being supported. But Alan's having the socket module catch that error and translate it a socket.error exception with an error message pointing the user to our socket module docs on the wiki (where he's added mention of this issue and the workaround)

So the workaround added is intended for those WinXP users, it's a global switch that turns off IPV6 results from getaddrinfo

This all looks great Alan, thanks for taking care of it! My only question, does this mean we now have complete ipv6 support (except for WinXP users)? Does that mean we should switch socket.has_ipv6 to True?