ipv6 addrinfo becomes a 4-tuple in python, with
additional scope-id and flowinfo members that are never
used in practice by normal apps. scope id might be used
once in a blue moon by something like a dhcp server
(use link local addresses).

this difference causes a large portion of work involved
in porting python apps to suppot v6. i suggest it be
changed to just an address-port tuple, or add some kind
of hack to allow it ot be unpacked like "host, port =
addr".

  -- erno kuusela <erno@iki.fi>

Logged In: YES 
user_id=21627

Why is this a bug, and what kind of large portion of work is
involved to support IPv6? Please have a look at
httplib/ftplib, which both support IPv6, with minimum amount
of work.

Logged In: YES 
user_id=16535

(sorry, title should have sockaddr and not addrinfo.)

It is a bug because it is gratuitous incompatibility between
6/4. "large portion" does not mean "huge absolute amount" -
just that at least for server apps otherwise you'd only need
to change a couple of lines and libraries expecting ipv4
sockets wouldn't know the difference. just grep 'host, port'
from most networking programs.

Logged In: YES 
user_id=21627

Closing as not-a-bug. RFC 3493 still lists flowinfo as being
present in an IPv6 address, so we should keep it. Removing
it now would break compatibility, anyway.