Re: [Discuss-gnuradio] Suppressing UHD prints

2015-07-06 Thread Koslowski, Sebastian (CEL)
On 07/06/2015 07:25 PM, Jared Dulmage wrote: > @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

Re: [Discuss-gnuradio] Suppressing UHD prints

2015-07-06 Thread Jared Dulmage
@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 pa

Re: [Discuss-gnuradio] Suppressing UHD prints

2015-07-02 Thread Koslowski, Sebastian (CEL)
On 07/01/2015 10:19 AM, Piotr Krysik wrote: > Hi all, > > UHD host library generates prints on the stdout. For example on each > retune I get something like: > > -- Tune Request: 959.00 MHz > -- The RF LO does not support the requested frequency: > -- Requested LO Frequency: 959.00 MH

[Discuss-gnuradio] Suppressing UHD prints

2015-07-01 Thread Piotr Krysik
Hi all, UHD host library generates prints on the stdout. For example on each retune I get something like: -- Tune Request: 959.00 MHz -- The RF LO does not support the requested frequency: -- Requested LO Frequency: 959.00 MHz -- RF LO Result: 958.998779 MHz -- Attempted to us