@Sebastion “Even if ’ uhd::msg::register_handler’ would be exposed to
python, you
still can’t drop-in your own null-handler. Swig doesn’t support
callbacks in the target language (python).”
This seems precisely what I have observed working with my example from
my question on 7/2/2015 “message passing: strobe or _post?” I use a
Python method as a callback given to .set_msg_handler. This is
certainly called when I use the message strobe to input a message to the
block, but not when using _post. Is this some new feature? Or am I
wrong that the operation is the same?
@Sebastion “Even if ’ uhd::msg::register_handler’ would be exposed to python,
you
still can’t drop-in your own null-handler. Swig doesn’t support
callbacks in the target language (python).”
This seems precisely what I have observed working with my example from my
question on 7/2/2015 “message passing: strobe or _post?” I use a Python method as
a callback given to .set_msg_handler. This is certainly called when I use
the message strobe to input a message to the block, but not when using _post. Is
this some new feature? Or am I wrong that the operation is the same?
Well SWIG not supporting it (see [1]) doesn’t mean one can’t write
custom code to run Python from the C end. Python blocks are implemented
via a gateway [2] to do this.