A bug, or lack of behavior in ServerSocket.py was
exposed while created a unit test for Python 2.3. As of
2.3, signals between threads propagate differently.
When cancelling a server that implemented threading
with a keyboard interrupt, the server would shut down
but not terminate (waiting on client threads).

The fit for this was to make the client threads
daemon-threads with the setDaemon call. Because this
was non-apparent, this patch adds a member variable
which acts as a hook and makes it clear that clients
need to either set or unset the variable when deriving
the class to control this behavior.

setDaemon is off by default, as this is thought to be
the consensus behavior.

Logged In: YES 
user_id=21627

Could you please provide changes to the documentation as
well (i.e. Doc/lib/libsocksvr.tex, and Misc/NEWS)?

There is a typo: 'chanegs' -> 'changes'

There is no need to attach the modified source to the patch;
the context diff is enough.

Logged In: YES 
user_id=116038

All Address in the new patch. See SocketServer.py.patch.2.

Logged In: YES 
user_id=21627

I recommend to approve this patch.

Logged In: YES 
user_id=21627

Thanks for the patch. Applied as

libsocksvr.tex 1.16
SocketServer.py 1.33
NEWS 1.532

Sorry it took so long.