[zeromq-dev] czmq python bindings and signals

[Wes Young]

[for search posterity]

i guess you can do something like this:

os.environ['ZSYS_SIGHANDLER'] = ‘false'

which is picked up by zsys_init when a socket or actor is init’d.

i think the real answer is still exposing more of zsys_* through zproc, but having trouble with some of the declarations through zproject (since we’re handing a zsys_handler_fn through the generated bindings, and not a basic type like int, char, etc..).

there are a few similar examples in the code (mainly with callbacks in constructors), but haven’t come across one that works, so will probably keep digging through those as time permits and see if i can’t conjure up a PR. seems like something minor, just need to find it.

> On Aug 1, 2016, at 2:00 PM, Wes Young <wes at barely3am.com> wrote:
> 
> my gut says exposing the zsys_* functions a bit more to the higher level languages seems like the way to go as far as generated bindings are concerned, but almost leads me to believe i’m missing something there too.. (the java work-around is confusing with this argument..).

--
wes
wesyoung.me

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20160808/37df55f2/attachment.sig>