Author michael.foord
Recipients aronacher, bethard, eric.smith, gregory.p.smith, loewis, marklodato, michael.foord, ncoghlan, orsenthil, r.david.murray, rickysarraf
Date 2009-09-14.19:58:07
SpamBayes Score 0.00688386
Marked as misclassified No
Message-id <1252958289.13.0.0505921922972.issue6247@psf.upfronthosting.co.za>
In-reply-to
Content
Command line parsing is a basic need, including amongst other standard
library modules. argparse has many advantages over optparse (not the
least of which is that it has an active maintainer). Several of these
features *can't* be added to optparse whilst maintaining backwards
compatibility, which is what prompted Steven to create argparse in the
first place.

Improvements that I am aware of include:

- handling of standard Windows way of specifying options
- sub-commands
- handling of positional arguments

I had to implement my own technique for handling a sub-command in recent
unittest changes that would have been much simpler if argparse were in
the standard library.
History
Date User Action Args
2009-09-14 19:58:09michael.foordsetrecipients: + michael.foord, loewis, gregory.p.smith, ncoghlan, orsenthil, bethard, eric.smith, aronacher, r.david.murray, rickysarraf, marklodato
2009-09-14 19:58:09michael.foordsetmessageid: <1252958289.13.0.0505921922972.issue6247@psf.upfronthosting.co.za>
2009-09-14 19:58:08michael.foordlinkissue6247 messages
2009-09-14 19:58:07michael.foordcreate