A problem with a multitude of sockets ending up in
TIME_WAIT when stressing a system with XML-RPC calls.
This can cause a Windows network to missbehave.

A solution on Windows platform is to set the sockopt
NOLINGER with parameters (1, 0) for the socket before
the socket is closed. This vill cause that Windows will
release the socket direct without going into TIME_WAIT.

The solution in code:
In httplib.py@somewhere:
NOLINGER = struct.pack('HH', 1, 0) # Release the
resource back to the system if socket closed

In httplib.py@632:
self.sock.setsockopt(socket.SOL_SOCKET,
socket.SO_LINGER, NOLINGER)
self.sock.close()   # close it manually... there may be
other refs

Logged In: YES 
user_id=352221

Read section, SO_LINGER at following address:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/winsock/wspsetsockopt_2.asp

Logged In: YES 
user_id=21627

Why do you want to avoid the TIME_WAIT state, and why do you
think it is a Python bug that it doesn't? See

http://www.developerweb.net/sock-faq/detail.php?id=13

where Richard Stevens himself explains that SO_LINGER should
*not* be used.

It might be that SO_REUSEADDR is sufficient, see

http://www.developerweb.net/sock-faq/detail.php?id=44

If you want xmlrpclib to use different socket options, you
should subclass httplib.HTTP to redefine either connect() or
close(), and you should subclass xmlrpclib.Transport to use
your subclassed transport.

Logged In: YES 
user_id=849994

Seems like Not a Bug.