Re: [Hamlib-developer] [Hamlib/Hamlib] ae9556: Fix debug messages shown even from disabled levels

[Daniele F. <iu...@gm...>]

Hello,

I have nothing against reverting this commit, but it doesn't work like
you said, in fact it also prints TRACE message if you set debug to
none and no error happened, but now I see that the reason for my
commit is that the old py3test.py used rigerror() instead of
rigerror2() so the output of the line
  print("status(str):\t\t%s" % Hamlib.rigerror(my_rig.error_status))
was unexpected to me.

>       assert Hamlib.rigerror(my_rig.error_status) == "Command completed successfully\n"
E       AssertionError: assert 'network.c(16...uccessfully\n' ==
'Command comp...uccessfully\n'
E
E         + network.c(1615): not starting multicast publisher
E         + *1:network.c(1616):network_multicast_publisher_start returning(0)
E         + *1:network.c(1798):network_multicast_receiver_start entered
E         + network.c(1810): multicast receiver address=0.0.0.0, port=4532
E         + network.c(1816): not starting multicast receiver
E         + *1:network.c(1817):network_multicast_receiver_start returning(0) ...
E
E         ...Full output truncated (14 lines hidden), use '-vv' to show

python/test_startup.py:34: AssertionError

I'll revert and also change the test to use rigerror2

-- 
73 de IU5HKX Daniele