@ Anders Langworthy wrote (2011-09-25 18:20+0200): > >> 2. Signal handling doesn't work [.] > >> I think this is an issue with python and not cherrypy. > >>[..] > >> (here with py2.7: ^C from keyboard doesn't work and signals sent from > >> "kill" (except SIGKILL are ignored). Process is not hung but must be > >> terminated with kill -9)
Yup! Wait for Py3K. Python radically blocks signals very often, especially during network transfers. Signals are even gobbled completely and disappear to hyperspace. You need to have the luck to get a "window" where the interpreter is actually responsive to signals (this is on Snow Leopard btw): > test: message 10 (3027/3733324 bytes) ^C [27 lines deleted] > test: message 165 (91276/1511996 bytes) ^C ====== PANIC: User forced program interruption Exception: KeyboardInterrupt (got it during a chomp()) --steffen
