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.

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.

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

> 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?

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.

> 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.

then change 'possible values' to 'for example'

Okay, this should now be clearer in r63057.