Expunge all uses of gflags

[GoogleCodeExporter]

Move to the argparse which works under both Python 2.x and 3.2.

Allows us to drop one dependency.

Original issue reported on code.google.com by jcgregorio@google.com on 11 Mar 2013 at 2:01

[GoogleCodeExporter]

And this removes a dependency not in the standard lib, which could be a nice 
ambition as well.

Original comment by dhermes@google.com on 11 Mar 2013 at 4:16

[GoogleCodeExporter]

Yes, it will also help with the port to Python 3.x since gflags isn't Python 
3.x compatible.

Original comment by jcgregorio@google.com on 11 Mar 2013 at 4:20

[GoogleCodeExporter]

The big question: is this a large enough change to qualify for a major version 
change, i.e. going to 2.0?

Original comment by jcgregorio@google.com on 11 Mar 2013 at 4:50

[GoogleCodeExporter]

IMO, no. I feel that our docs suggest safe ways to get the most up to date 
version of the code and so having some files out-of-date that rely on gflags is 
not likely.

Empirical evidence suggests (to me) that people aren't actively extending the 
gflags pieces we use (never seen a thing about it on StackOverflow, never had 
any dev ask me about it, etc.), so I don't see it as a (large-ly) breaking 
change.

I think an upgrade to 2.0 should only be forced by big changes, such as a 
change in an interface that people use to interact with the code.

Original comment by dhermes@google.com on 11 Mar 2013 at 6:07

[GoogleCodeExporter]

Maybe we should post to the forum?

Original comment by dhermes@google.com on 11 Mar 2013 at 6:07

[GoogleCodeExporter]

Will go out in 1.2.

Original comment by jcgregorio@google.com on 5 Aug 2013 at 2:02

• Changed state: Fixed