CLI arg typecasting about invoke HOT 2 CLOSED

I have a partial implementation of this in master, which infers typing from the default value of arguments (both in terms of a task's argspec, and at the parser level, e.g. if anybody were to construct the parser arguments manually).

Still needs to be expanded to allow something explicit for any args that lack default values.

from invoke.

Years-later clarification: the "partial implementation" mentioned above has been a core part of the CLI framework for a long time and seems to work OK for many/most use cases; it's the functionality that knows when you have:

@task
def mytask(c, count=5):
    pass

then this invocation results in count=7 and not count="7":

$ inv mytask --count 7

Combined with boolean true-flags (--bool/--no-bool) and the recently solved #9 for lists (--mylist a --mylist b --mylist c yielding ["a", "b", "c"]) this doesn't leave much but edge cases, which deserve their own ticket(s) anyways.

Things like "no I really want SHORTER ways to supply lists" (can be solved on the user's end with split), dicts (kinda ditto, though we could possibly supply well-tested helpers for parsing eg --mydict=key=val,otherkey=otherval) and etc.

from invoke.