I am planning to migrate the CLI tool from PyUAVCAN into a separate package because it complicates maintenance and violates the sensible design principle “do one thing but do it well”. Doing so is easy because the CLI is barely coupled with the library at all, it only relies on its public APIs.
If the CLI tool is to become a separate entity, it is to require a name. I am inclined to name it u
because who has time to type letters in 2021?
u sub uavcan.node.Heartbeat
u call 42 123.sirius_cyber_corp.PerformLinearLeastSquaresFit.1.0 '{points: [{x: 10, y: 1}, {x: 20, y: 2}]}'
u pub 12345.uavcan.si.sample.temperature.Scalar.1.0 '{kelvin: 123.456}' --count=2
If there are any objections, speak up now. The question is relevant right now because I want the first release of PyUAVCAN to be devoid of CLI.
FYI @scottdixon
Edit: upon some deliberation I am inclined to prefer un
as an acronym for “uncomplicated” or UavcaN, since this name is actually available at PyPI. I messaged the current owner of the placeholder at u
just to check if he is interested in transferring the name to us but the chances are slim.