OK, I'll investigate that soon. I just spent a few minutes looking through
the call trees, and it seems like every path leads to getsockaddrarg, which
calls setipaddr, which *might* call getaddrinfo. So I have to really
understand how that path works on a socket that's been connected like
s.connect(("104.130.43.121", 80))
On Tue, Feb 23, 2016 at 10:44 PM, Guido van Rossum <[email protected]> wrote:
> No, I'm worried that the C code that eventually gets called with e.g.
> "104.130.43.121" as the "host" were makes another call to
> getaddrinfo().
>
> On Tue, Feb 23, 2016 at 6:40 PM, A. Jesse Jiryu Davis
> <[email protected]> wrote:
> > Guido I don't quite understand — what's your concern here? Are you
> worried
> > my new _ipaddr_info() function might return an incorrect tuple that
> differs
> > from a real getaddrinfo() return value?
> >
> > On Tue, Feb 23, 2016 at 12:24 PM, Guido van Rossum <[email protected]>
> wrote:
> >>
> >> W00t! Hopefully when you connect a socket it actually believes the
> >> pre-parsed address.
> >>
> >> --Guido (mobile)
> >
> >
>
>
>
> --
> --Guido van Rossum (python.org/~guido)
>
