umv: wrong error message when move fails
code for calc_mot5
in MR !3147 (merged)
BLISS [2]: calc_mot5.move(2)
!!! === TypeError: unsupported operand type(s) for /: 'NoneType' and 'int' === !!! ( for more details type cmd 'last_error' )
BLISS [3]: umv(calc_mot5,2)
!!! === RuntimeError: intended usage: umv(motor1, target_position_1, motor2, target_position_2, ... ) === !!! ( for more details type cmd 'last_error' )
BLISS [4]: type(calc_mot5)
Out [4]: <class 'bliss.common.axis.Axis'>
In fact umv
should not hide this error ... I think the problem is typeguard
in case. typeguard
should not raise a general TypeError
but something more specific. I think we discussed about this a while ago an thought about patching the typeguard
module or providing a patch on github...
Edited by Linus Pithan