argparse

Here is my argparse sample say sample.py import argparse parser = argparse.ArgumentParser() parser.add_argument("-p", nargs="+", help="Stuff") args = parser.parse_args() print args Python - 2.7.3 I expect that the user supplies a list of arguments separated by spaces after the -p option. For example, if you run $ sample.py -p x y Namespace(p=['x', 'y']) But my problem is that when you run $ sample.py -p x -p y Namespace(p=['y']) Which is neither here nor there. I would like one of the following Throw an exception to the user asking him to not use -p twice instead just supply them as one

How do I specify the position of a positional argument? In my example below, the SCR & SCV arguments appear at the end of the optional arguments, I want them to appear at the beginning. #!/usr/bin/python import argparse ### Parse arguments ### parser = argparse.ArgumentParser() parser.add_argument("SCR",type=int) parser.add_argument("SCV",type=int) parser.add_argument("--itemid",nargs='?') parser.add_argument("--tkt",nargs='?') parser.add_argument("--rfc",nargs='?') parser.add_argument("--state",nargs='?') parser.add_argument("--vendor",nargs='?') parser.add_argument("--application",nargs='?')

The below paste contains relevant snippets from three separate Python files. The first is a script called from the command line which instantiates CIPuller given certain arguments. What happens is that the script gets called with something like: script.py ci (other args to be swallowed by argparse). The second is part of a subclass called Puller . The third is part of a subclass of Puller called CIPuller . This works wonderfully, as the correct subclass is called, and any user using the wrong other args gets to see the correct args for their given subclass, plus the generic arguments from the

If I have an optional argument with optional argument value, is there a way to validate if the argument is set when the value is not given? For instance: parser = argparse.ArgumentParser() parser.add_argument('--abc', nargs='?') args = parser.parse_args() Would correctly give me: optional arguments: --abc [ABC] How do I distinguish between 1 and 2 below? '' => args.abc is None '--abc' => args.abc is still None '--abc something' => args.abc is something ... Update: Found a trick to solve this problem: you can use "nargs='*'" instead of "nargs='?'". This way #1 would return None, and #2 would

Is there any way I can tell argparse to not eat quotation marks? For example, When I give an argument with quotes, argparse only takes what's inside of the quotes as the argument. I want to capture the quotation marks as well (without having to escape them on the command line.) pbsnodes -x | xmlparse -t "interactive-00" produces interactive-00 I want "interactive-00" wim I think it is the shell that eats them, so python will actually never see them. Escaping them on the command line may be your only option. If it's the \"backslash\" style escaping you don't like for some reason, then this way

I have the following test-code import argparse parser = argparse.ArgumentParser() parser.add_argument("--verbose", default = 0, type=int) subparsers = parser.add_subparsers(dest = "parser_name") parser_lan = subparsers.add_parser('car') parser_lan.add_argument("--boo") parser_lan.add_argument("--foo") parser_serial = subparsers.add_parser('bus') parser_serial.add_argument("--fun") print parser.parse_args() which defines two sub-parsers, having a different set of arguments. When I call the testcode as tester.py --verbose 3 car --boo 1 --foo 2 I get the expected result Namespace(boo='1', foo='2'