See if http://crrev.com/1063243002 can be reused here (early work on the same issue).

Plan of action:

In logging_utils.py, bring ArgumentParserWithLogging to feature parity with OptionParserWithLogging:

https://code.google.com/p/chromium/codesearch#chromium/infra/luci/client/utils/logging_utils.py&q=luci%20optparse&sq=package:chromium&dr=C&l=225

Then upgrade all the users of OptionParserWithLogging to ArgumentParserWithLogging:

https://code.google.com/p/chromium/codesearch#search/&q=OptionParserWithLogging%20file:%5Einfra/luci/&sq=package:chromium&type=cs

and finally hunt down all the direct use of optparse:

https://code.google.com/p/chromium/codesearch#search/&q=optparse%20file:%5Einfra/luci/&sq=package:chromium&type=cs

Some clients may be ready for ts_mon before the entire migration is complete, so plan accordingly.

Not actively working on this, making available.

If this is really a Pri-1, find an owner and update the priority.

This is the result of a bulk edit that moved high priority available bugs to a lower priority in an attempt to be more honest with bug filers.

I don't think this should be a Monitoring bug.  Individual clients should migrate to argparse when they need to.

Well, except this was a blocker for issue 610006... Reopening and assigning to swarming component.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Still a nice-to-have, as long as we have clients in Python. But maybe they'll go away in time...