Nate Pease [X] can we bump the priority on this please? The longer we go without people using the new version the more chance we have of finding problems earlier rather than waiting until November.

ok

pipetask had options `-i/\–-input and -o/--output, but -i conflicted with butler's -i/--instrument, so I removed the -i from --input. Assuming that's what we want, does it make sense to leave the -o flag for --output? I think it may be confusing to have that but to have -i mean something other than input. Or, I could change the --instrument short flag, but that might be a bigger change than we want?

Andy can you please review these changes?

Pending the answer to the question about the -o flag, there maybe a bit more work to do for this ticket if we decide to not use -o for --output (or change --instrument's -i).

Looks OK, though I have a concern for --long-log which is now a global option. For old pipetask we specifically decided that all options have to be per-sub-command options to avoid confusion.

Old pipetask had only long option for an instrument, and short -i option for --input. We could keep that convention or add short -I (capital) for an instrument (and I know all reasons why capital I is bad).

Of course that would still be inconsistent with the butler command, which we are trying to avoid.

Well, pipetask is going to be used much more frequently than butler and in that respect consistency between -i and -o in pipetask is more important than consistency for -i between pipetask and butler.