Hi Brian, >> Thus, I think the only way of resolving this if 0MQ is making out >> signals in the IO threads. Thoughts? > > What I meant was... > > Thus, I can't think of any way of resolving this if 0MQ is masking out > signal in the IO threads. > > After looking a bit more, I think it might be possible to install a > signal handler at the C-level > that replaces Python's default signal handler and does the right > thing. I know another project > that does this with some success. I am contacting them about this. > But, it would be nice > to not have to do this...
So what do you propose? As far as I understood from the previous email, Python is actually getting the signals, however, it deliberately chooses to delay their processing till the C function exits. How can 0MQ possibly help with that? Martin _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
