can't specify address family, may use the wrong one about pystatsd HOT 8 CLOSED

Interesting point, especially since localhost will usually resolve to ::1 first. Hmm.

The official StatsD server seems to only support one of v4 or v6 at a time. Maybe we need a boolean ipv6 flag, that defaults to False like the server, and then specify the family in the socket.getaddrinfo. Then it's possible that socket.getaddrinfo will raise a socket.gaierror, but that's probably OK.

from pystatsd.

Hide ipv6 behind the flag seems like a good idea :).

from pystatsd.

852c849

from pystatsd.

Was this issue ever solved? Commit 852c849 doesn't seem to have anything to do with this.

from pystatsd.

You're absolutely right, it was e78b046, which is not on PyPI yet

from pystatsd.

Thanks @jsocol ! Any timeframe for the release of 3.2 to PyPi?

from pystatsd.

I don't really know why I didn't do it in March. Once #63 is wrapped up I'll push the new version.

from pystatsd.

Sounds good, thanks @jsocol!

from pystatsd.