This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients bethard, eric.smith, gregory.p.smith, loewis, marklodato, michael.foord, ncoghlan, orsenthil, r.david.murray, rickysarraf
Date 2009-09-12.03:13:45
SpamBayes Score 1.24149e-07
Marked as misclassified No
Message-id <>
Only +0 purely because I haven't used argparse myself yet.

Otherwise I would probably be +1, since I have several scripts that have
fairly kludgy hacked together optparse based approaches to handling
positional arguments, subparsers and building new parsers that accept
the superset of options defined in existing parsers. The feature
comparison between argparse and optparse makes it sound like argparse
does a much better job of supporting these use cases.

The reasons I don't use argparse for them are that: a) I didn't know it
existed until recently; and b) the scripts are in an environment where
getting approval to use new third party modules is something of a pain.
Date User Action Args
2009-09-12 03:13:48ncoghlansetrecipients: + ncoghlan, loewis, gregory.p.smith, orsenthil, bethard, eric.smith, r.david.murray, michael.foord, rickysarraf, marklodato
2009-09-12 03:13:47ncoghlansetmessageid: <>
2009-09-12 03:13:46ncoghlanlinkissue6247 messages
2009-09-12 03:13:45ncoghlancreate