Reconsider positional args about invoke HOT 3 CLOSED

Aww yiss. It works! Also some refactoring and such which is probably a net gain.

from invoke.

dstufft pointed out that users are likely to expect any non-default-value args will show up as positionals; i.e. in:

@task
def mytask(foo, bar='baz'): pass

You would have to invoke it as mytask --foo fooval regardless of whether you needed to override bar, analogous to always calling it at the Python level as mytask(foo='fooval').

While this may be good practice, it is restrictive and goes against common patterns (i.e. in this situation at the Python level the average coder is more likely to invoke mytask('fooval').

Counterpoint is that if we assumed all non-default-value args become positional args, task authors lose ability to force the more explicit flag versions.

Sounds like best idea is then to default to no-default-is-positional, but retain @task(positional=[xxx]) as an option for fine tuning.

from invoke.

Only thing that is annoying is how my existing test suite had to add positional=[] in a bunch of spots. Adding new ticket for global control of this.

from invoke.