Positional vs Keyword parameters
Python allows for keyword arguments (arguments with default values) to be specified positionally.
That complicates addition or removal of new keyword arguments since such changes must account for their possible
Moreover, in case of our Interface’s, it contributes to inhomogeneity since when used in CLI, all keyword
must be specified via non-positional
--<option>’s, whenever Python interface allows for them to be used
Python 3 added possibility to use a
* separator in the function definition to mandate that all keyword arguments
after it must be be used only via keyword (
It is encouraged to use
* to explicitly separate out positional from keyword arguments in majority of the cases,
and below we outline two major types of constructs.
Subclasses of the
Interface provide specification and implementation for both
CLI and Python API interfaces.
All new interfaces must separate all CLI
--options from positional arguments using
* in their
Note: that some positional arguments could still be optional (e.g., destination
and thus should be listed before
*, despite been defined as a keyword argument in the
A unit-test will be provided to guarantee such consistency between CLI and Python interfaces. Overall, exceptions to this rule could be only some old(er) interfaces.
Regular functions and methods
* is encouraged for any function (or method) with keyword arguments.
* should come before the first keyword argument, but similarly to the Interfaces above, it is left to
the discretion of the developer to possibly allocate some (just few) arguments which could be used positionally if