Certain CLI parsers, such as FSL's Eddy, implement a rigid formulation where only equal-separated options (--long-option=value) are accepted and space-separated ones (--long-option value) are rejected. Pydra implements space-separated options, which are common to short and long option names in modern standards.
Sadly, this complicates specification definition slightly with repetition:
Certain CLI parsers, such as FSL's Eddy, implement a rigid formulation where only equal-separated options (
--long-option=value
) are accepted and space-separated ones (--long-option value
) are rejected. Pydra implements space-separated options, which are common to short and long option names in modern standards.Sadly, this complicates specification definition slightly with repetition:
There is a notion of separator in Pydra's field metadata, but it is used for lists of values.
Maybe we could introduce an option separator (defaults to whitespace if unspecified), such as: