[Python-Dev] Pronouncement on PEP 389: argparse? (original) (raw)
Olemis Lang olemis at gmail.com
Mon Dec 14 20:35:21 CET 2009
- Previous message: [Python-Dev] Pronouncement on PEP 389: argparse?
- Next message: [Python-Dev] Pronouncement on PEP 389: argparse?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Dec 14, 2009 at 2:11 PM, Michael Foord <fuzzyman at voidspace.org.uk> wrote:
On 14/12/2009 19:04, Ian Bicking wrote:
[snip...] Another thing I just noticed is that argparse using -v for version where optparse does not (it only adds --version); most of my scripts that use -v to mean --verbose, causing problems. Since this is a poll question on the argparse site I assume this is an outstanding question for argparse, but just generally I think that doing things the same way as optparse should be preferred when at all reasonable. I also use -v for verbose in a few scripts (including options to unittest when run with python -m). I've seen -V as a common abbreviation for --version (I've just used this with Mono for example).
Many Unix commands accept these switches too . AFAICR there was an standard (well ...) set of command line options for Unix systems (can't find a link :-/ )
.. [1] Command-Line Options (http://www.faqs.org/docs/artu/ch10s05.html)
-- Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/
Featured article: Automated init. - http://bitbucket.org/osimons/trac-rpc-mq/changeset/e122336d1eb2/
- Previous message: [Python-Dev] Pronouncement on PEP 389: argparse?
- Next message: [Python-Dev] Pronouncement on PEP 389: argparse?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]