WinNT4 -- don't have other platforms to hand.

If I hit Ctrl-C in the roundup-server console 
window, the resulting KeyboardInterrupt doesn't 
appear to be caught and acted on until the next 
HTTP request hits the server.

I suspect this is more a Python socket library 
problem -- my guess is that the KeyboardInterrupt 
doesn't interrupt socket.listen -- than a Roundup 
problem...

Logged In: YES 
user_id=6405

Yeah, and since I don't have control over the signals on Windows, I'm not sure I can do anything about this.

Unless any suggestions pop up in the near future (say, a week), I'll close this issue. Hurm. Need to be able to resolve it as "Can't Fix"...

Logged In: YES 
user_id=707416

I assume you are using a native Windows python as Cygwin
python 
responds to the ^C immediately.

I know the cygwin folks put a lot 
of effort into signal handling
and being able to interrupt winsock 
(windows sockets)
calls, so Richard quite likely can't do anything 
about this.