some errors bring down the whole interpreter

[m0n5t3r]

In certain situations, pyzmq aborts with a cryptic message and brings down python, instead of raising an exception; examples:

• call zmq.Context() more than once in the same Python process
• random, but reliable failures when attempting to have several DOWNSTREAM threads pushing data to an UPSTREAM collector

I am not sure this can be managed at the bindings level, but if it can, please do :) (or tell me where to look, I am willing to get my hands dirty)

[minrk]

Some more details on your zeromq and pyzmq versions/builds and OS would be helpful.

Are you using zeromq-2.0.10 and pgm? The version of openpgm with zeromq-2.0.10 doesn't allow multiple contexts, and will crash if you try to create more. This is fixed in 2.1.0 (and possibly also the 'maint' git branch).

In general, zeromq-2.0 has quite a few c-asserts that bring down the process, and there's not much we can do about it. zeromq-2.1 is much better behaved in that respect, and even responds nicely to KeyboardInterrupts.

[m0n5t3r]

oops, sorry... I'm using 2.0.10 on Ubuntu from ppa:chris-lea/zeromq, probably has PGM compiled in; I solved the multiple contexts problem by making the context a singleton, but there are other things that crash the process and making something work involves a lot of voodoo

I guess I'll have to wait for the release of 2.1 then :-/ (or package a beta for myself)

[minrk]

There was a beta release of 2.1.0 in December, and as far as my experience, it's better across the board than 2.0.10. I would personally recommend using that over 2.0.10, even though it's beta. The usual arguments against beta are stability, etc., but 2.1.0 is much more stable than 2.0.10.

Closing the issue, since it doesn't apply to current versions.