Sorry, not navigating this bug tracker too well.  Above is a patch.  :)

And here's the corresponding Mozilla bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=613813

I understand what you need. But this sounds specific to your test suite 
architecture. For now, could you try having some stub python code that masks 
SIGINT on your side? Will this work for you?

e.g.

pywebsocket_ignore_sigint.py
====
import signal

from mod_pywebsocket.standalone import _main

if __name__ == '__main__':
  signal.signal(signal.SIGINT, signal.SIG_IGN)
  _main()
====

If I understand your problem correctly, it might solve the problem to have a 
functionality to launch a stand-alone server as a daemon process.

I think daemonization would be a valid feature request, and we probably should 
implement it.
(I think daemonization will only work on Unix (and will not on Windows), but I 
hope this limitation won't block your use cases)

> If I understand your problem correctly, it might solve the problem to have a 
> functionality to launch a stand-alone server as a daemon process.

Could you elaborate on this?  If it only works on *nix, that's fine with me.  :)

daemon() is basically a combination of fork and setsid. A daemon process is 
separated from its parent and belongs to a new process group, thus signals to 
the parent process will no longer reach the child (daemon) process.

I hope this clarifies your question.

Oh, I see.  Yes, I think daemon() would solve the problem.  In the meantime, 
we'll probably just use a wrapper script.