[issue1685962] socket.getaddrinfo() should take an address tuple.

Giampaolo Rodola' report at bugs.python.org
Sat Jul 10 12:53:30 CEST 2010


Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

I think the original reason why getaddrinfo() has been designed to accept separate host and port args instead of a tuple is because the original C call does the same:
http://www2.research.att.com/~gsf/man/man3/getaddrinfo.html

Despite this apparently looks somewhat inconsistent with other calls like bind(), connect() and connect_ex() which take an address tuple, they reflect the original C behavior in the same manner, also because they're fundamentally different than getaddrinfo(), so I see no valid reason to change this situation.

----------
nosy: +giampaolo.rodola

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue1685962>
_______________________________________


More information about the Python-bugs-list mailing list