Type conversions about docopt HOT 3 CLOSED

int(options["<x>"]) is what I have in some of my throw-away scripts, and I'm not totally happy with this.

However there is little overhead in using schema. Compare:

• your API:

args = docopt(__doc__, conversions={'<x>': int, '<y>': int})

• docopt with schema:

Int = Or(None, Use(int))
args = Schema({'<x>': Int, '<y>': Int}).validate(docopt(__doc__))

And the more complex your CLI is—the smaller is the relative overhead.

Also, I have never seen a program that takes arbitrary integers—except for calculators—it is always a range or a set, which you can express easily with schema:

schema = Schema({'<x>': And(Use(int), lambda n: n in [2**n for n in range(10)]))

from docopt.

As said on Reddit: I'm almost convinced, yet I still think it's not DRY that way: you have to tell schema which arguments are optional, while docopt already knows about that.

from docopt.

As I said somewhere before—I prefer to err on the side of simplicity. Anyway, thanks for suggestion—more of that is always welcome.

from docopt.