[issue31198] getaddrinfo: inconsistent handling of port=None

Nathaniel Smith added the comment: Ugh, apparently this weird behavior is actually mandated by the RFC :-(. RFC 3493: The nodename and servname arguments are either null pointers or pointers to null-terminated strings. One or both of these two arguments must be a non-null pointer.

[issue31198] getaddrinfo: inconsistent handling of port=None

Changes by Nathaniel Smith : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___

[issue31198] getaddrinfo: inconsistent handling of port=None

New submission from Nathaniel Smith: socket.getaddrinfo accepts None as a port argument, and translates it into 0. This is handy, because bind() understands 0 to mean "pick a port for me", and if you want bind to pick a port for you and port=None is a slightly more obvious way to say that