Sept. 11, 2009
8:59 a.m.
Nick Coghlan wrote:
Anyone wanting to replace/compete with optparse (particularly with goals for latter standard library inclusion) would do well to better articulate what they don't like about optparse though. I acknowledge that using optparse the first couple of times can have something of a learning curve, but that's because it is rather powerful.
Note that argparse does provide that justification: http://argparse.googlecode.com/svn/trunk/doc/argparse-vs-optparse.html In particular: http://argparse.googlecode.com/svn/trunk/doc/argparse-vs-optparse.html#upgra... has a short blurb on why Steven didn't just extend optparse. He tried to, but decided it was easier if he didn't. Eric.