documentation -- do serversockets work with ipv6

[mrm]

BPO	2741
Nosy	@loewis, @birkenfeld

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/birkenfeld'
closed_at = <Date 2008-05-11.10:59:51.115>
created_at = <Date 2008-05-02.18:53:13.041>
labels = ['docs']
title = 'documentation -- do serversockets work with ipv6'
updated_at = <Date 2008-05-11.10:59:51.114>
user = 'https://bugs.python.org/mrm'

bugs.python.org fields:

activity = <Date 2008-05-11.10:59:51.114>
actor = 'georg.brandl'
assignee = 'georg.brandl'
closed = True
closed_date = <Date 2008-05-11.10:59:51.115>
closer = 'georg.brandl'
components = ['Documentation']
creation = <Date 2008-05-02.18:53:13.041>
creator = 'mrm'
dependencies = []
files = []
hgrepos = []
issue_num = 2741
keywords = []
message_count = 8.0
messages = ['66102', '66105', '66133', '66143', '66275', '66290', '66291', '66621']
nosy_count = 3.0
nosy_names = ['loewis', 'georg.brandl', 'mrm']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue2741'
versions = ['Python 2.5']

[mrm]

the url
http://docs.python.org/lib/node633.html
states

1. address_family
   The family of protocols to which the server's socket belongs.
   socket.AF_INET and socket.AF_UNIX are two possible values.

would suggest including socket.AF_INET6 as well if it is supported
or what criteria makes a socket not usable with this class.

[loewis]

I fail to see the issue. There are many other address families supported
as well, such as AF_BLUETOOTH, AF_PACKET, AF_TIPC, and AF_NETLINK,
depending on the system. The documentation just lists some examples.

[mrm]

Martin v. Löwis wrote:

Martin v. Löwis <martin@v.loewis.de> added the comment:

I fail to see the issue. There are many other address
families supported as well, such as AF_BLUETOOTH, AF_PACKET,
AF_TIPC, and AF_NETLINK, depending on the system. The
documentation just lists some examples.

the way i read the text, i gathered that it might not work
with sockets belonging to a subset of address families.

thanks,
mike

[loewis]

the way i read the text, i gathered that it might not work
with sockets belonging to a subset of address families.

I still cannot see anything wrong with that text, but then,
English is not my native language. Can you suggest a different
formulation?

[mrm]

so i suggest just removing this sentence --

AF_INET and socket.AF_UNIX are two possible values.

this would imply that all socket address families are supported.
but if that is not true just list the exceptions.

[loewis]

so i suggest just removing this sentence --

AF_INET and socket.AF_UNIX are two possible values.

this would imply that all socket address families are supported.
but if that is not true just list the exceptions.

I think this will confuse users which don't know what an
"address family" is - they are left guessing what possibly could
be in this field.

[mrm]

then change 'possible values' to 'for example'

[birkenfeld]

Okay, this should now be clearer in r63057.