This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author giampaolo.rodola
Recipients amak, giampaolo.rodola
Date 2010-07-10.10:53:27
SpamBayes Score 0.026964406
Marked as misclassified No
Message-id <1278759210.3.0.467921394588.issue1685962@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2010-07-10 10:53:30giampaolo.rodolasetrecipients: + giampaolo.rodola, amak
2010-07-10 10:53:30giampaolo.rodolasetmessageid: <1278759210.3.0.467921394588.issue1685962@psf.upfronthosting.co.za>
2010-07-10 10:53:28giampaolo.rodolalinkissue1685962 messages
2010-07-10 10:53:27giampaolo.rodolacreate