Paul Marks added the comment:
> if the user specifically wants to bind to a numeric IPv4 address, is there
> any advantage of choosing the dual-stack [...]?
If you're in a position to write AF_INET6-only code, then dualstack sockets can
make things a bit cleaner (one family for
Paul Marks added the comment:
First off, the server_address=('localhost', port) case: this feature is
fundamentally broken without support for multiple sockets, because the server
can listen on at most one address, and any single choice will often be
inconsistent with clients' expectations
Changes by Paul Marks <pma...@google.com>:
--
nosy: +Paul Marks
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue20215>
___
__
New submission from Paul Marks:
Python's web servers were formerly reachable from IPv6 clients, as evidenced by
this example code for socket.getaddrinfo():
https://docs.python.org/3/library/socket.html#socket.getaddrinfo
But today, www.python.org is IPv4-only:
import socket
