Should test_socket require the network resource
be enabled?  It only works for me when I'm
connected (Running an old slackware linux).
This is true of both CVS and 2.2 python

When not connected testHostnameRes fails because
getfqdn() returns my hostname, 'zazz', but
gethostbyaddr(ip) returns the hostname 'localhost'.
When I am connected getfqdn() also returns
'localhost' so there's no problem.  It could be
fixed for me by either requiring the network
resource or changing line 234 of test_socket from:
all_host_names = [hname] + aliases
to:
all_host_names = [hname, hostname] + aliases

Or maybe my machine's setup is just messed
up in which case I trust you'll close the bug.

Logged In: YES 
user_id=357491

The purpose of the network resource if for when you need to 
connect to the Internet, not to use sockets so the test is correct 
in that regard.

Logged In: YES 
user_id=357491

This can either be considered invalid because of my previous comment 
explaining why the 'network' resource is not appropriate for test_socket, or 
it can be considered fix since I just coincidentally fixed test_socket in the 
exact same way Michael suggested.

Either way it is now closed.