Greetings,
With PyZMQ versions prior to 13.0.0, we were running into problems with
certain PyZMQ calls getting interrupted by restartable signals (e.g.,
SIGALRM) used by our application. We fixed this problem like this:
while True:
try:
On Mar 11, 2013, at 13:13, Jonathan Kamens jkam...@quantopian.com wrote:
Greetings,
With PyZMQ versions prior to 13.0.0, we were running into problems with
certain PyZMQ calls getting interrupted by restartable signals (e.g.,
SIGALRM) used by our application. We fixed this problem like
To further clarify, there are two cases:
1. no sigint handler registered - ^C absolutely should result in
KeyboardInterrupt. This behavior is intended, and has not changed since
2.1.9.
2. sigint handler registered - in this case, KeyboardInterrupt should *not*
be raised, and the regular
Great!
I didn't noticed PR 338.. So it's really fully fixed in master.
2013/3/11 MinRK benjami...@gmail.com
To further clarify, there are two cases:
1. no sigint handler registered - ^C absolutely should result in
KeyboardInterrupt. This behavior is intended, and has not changed since
