p!ranha?

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>15.4. argparse — Parser for command-line options, arguments and sub-commands — Python 2.7.5 documentation</title> <link rel="stylesheet" href="../_static/default.css" type="text/css" /> <link rel="stylesheet" href="../_static/pygments.css" type="text/css" /> <script type="text/javascript"> var DOCUMENTATION_OPTIONS = { URL_ROOT: '../', VERSION: '2.7.5', COLLAPSE_INDEX: false, FILE_SUFFIX: '.html', HAS_SOURCE: true }; </script> <script type="text/javascript" src="../_static/jquery.js"></script> <script type="text/javascript" src="../_static/underscore.js"></script> <script type="text/javascript" src="../_static/doctools.js"></script> <script type="text/javascript" src="../_static/sidebar.js"></script> <link rel="search" type="application/opensearchdescription+xml" title="Search within Python 2.7.5 documentation" href="../_static/opensearch.xml"/> <link rel="author" title="About these documents" href="../about.html" /> <link rel="copyright" title="Copyright" href="../copyright.html" /> <link rel="top" title="Python 2.7.5 documentation" href="../index.html" /> <link rel="up" title="15. Generic Operating System Services" href="allos.html" /> <link rel="next" title="15.5. optparse — Parser for command line options" href="optparse.html" /> <link rel="prev" title="15.3. time — Time access and conversions" href="time.html" /> <link rel="shortcut icon" type="image/png" href="../_static/py.png" /> <script type="text/javascript" src="../_static/copybutton.js"></script> </head> <body> <div class="related"> <h3>Navigation</h3> <ul> <li class="right" style="margin-right: 10px"> <a href="../genindex.html" title="General Index" accesskey="I">index</a></li> <li class="right" > <a href="../py-modindex.html" title="Python Module Index" >modules</a> |</li> <li class="right" > <a href="optparse.html" title="15.5. optparse — Parser for command line options" accesskey="N">next</a> |</li> <li class="right" > <a href="time.html" title="15.3. time — Time access and conversions" accesskey="P">previous</a> |</li> <li><img src="../_static/py.png" alt="" style="vertical-align: middle; margin-top: -1px"/></li> <li><a href="http://www.python.org/">Python</a> »</li> <li> <a href="../index.html">Python 2.7.5 documentation</a> » </li> <li><a href="index.html" >The Python Standard Library</a> »</li> <li><a href="allos.html" accesskey="U">15. Generic Operating System Services</a> »</li> </ul> </div> <div class="document"> <div class="documentwrapper"> <div class="bodywrapper"> <div class="body"> <div class="section" id="module-argparse"> <h1>15.4. <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> — Parser for command-line options, arguments and sub-commands<a class="headerlink" href="#module-argparse" title="Permalink to this headline">¶</a></h1> New in version 2.7. Source code: <a class="reference external" href="http://hg.python.org/cpython/file/2.7/Lib/argparse.py">Lib/argparse.py</a> <hr class="docutils" /> <div class="sidebar"> Tutorial This page contains the API reference information. For a more gentle introduction to Python command-line parsing, have a look at the <a class="reference internal" href="../howto/argparse.html#id1">argparse tutorial</a>. </div> The <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> module makes it easy to write user-friendly command-line interfaces. The program defines what arguments it requires, and <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> will figure out how to parse those out of <a class="reference internal" href="sys.html#sys.argv" title="sys.argv"><tt class="xref py py-data docutils literal">sys.argv</tt></a>. The <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> module also automatically generates help and usage messages and issues errors when users give the program invalid arguments. <div class="section" id="example"> <h2>15.4.1. Example<a class="headerlink" href="#example" title="Permalink to this headline">¶</a></h2> The following code is a Python program that takes a list of integers and produces either the sum or the max: <div class="highlight-python"><div class="highlight"><pre>import argparse parser = argparse.ArgumentParser(description='Process some integers.') parser.add_argument('integers', metavar='N', type=int, nargs='+', help='an integer for the accumulator') parser.add_argument('--sum', dest='accumulate', action='store_const', const=sum, default=max, help='sum the integers (default: find the max)') args = parser.parse_args() print args.accumulate(args.integers) </pre></div> </div> Assuming the Python code above is saved into a file called <tt class="docutils literal">prog.py</tt>, it can be run at the command line and provides useful help messages: <div class="highlight-python"><pre>$ prog.py -h usage: prog.py [-h] [--sum] N [N ...] Process some integers. positional arguments: N an integer for the accumulator optional arguments: -h, --help show this help message and exit --sum sum the integers (default: find the max)</pre> </div> When run with the appropriate arguments, it prints either the sum or the max of the command-line integers: <div class="highlight-python"><pre>$ prog.py 1 2 3 4 4 $ prog.py 1 2 3 4 --sum 10</pre> </div> If invalid arguments are passed in, it will issue an error: <div class="highlight-python"><pre>$ prog.py a b c usage: prog.py [-h] [--sum] N [N ...] prog.py: error: argument N: invalid int value: 'a'</pre> </div> The following sections walk you through this example. <div class="section" id="creating-a-parser"> <h3>15.4.1.1. Creating a parser<a class="headerlink" href="#creating-a-parser" title="Permalink to this headline">¶</a></h3> The first step in using the <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> is creating an <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> object: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(description='Process some integers.') </pre></div> </div> The <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> object will hold all the information necessary to parse the command line into Python data types. </div> <div class="section" id="adding-arguments"> <h3>15.4.1.2. Adding arguments<a class="headerlink" href="#adding-arguments" title="Permalink to this headline">¶</a></h3> Filling an <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> with information about program arguments is done by making calls to the <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> method. Generally, these calls tell the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> how to take the strings on the command line and turn them into objects. This information is stored and used when <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> is called. For example: <div class="highlight-python"><div class="highlight"><pre>>>> parser.add_argument('integers', metavar='N', type=int, nargs='+', ... help='an integer for the accumulator') >>> parser.add_argument('--sum', dest='accumulate', action='store_const', ... const=sum, default=max, ... help='sum the integers (default: find the max)') </pre></div> </div> Later, calling <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> will return an object with two attributes, <tt class="docutils literal">integers</tt> and <tt class="docutils literal">accumulate</tt>. The <tt class="docutils literal">integers</tt> attribute will be a list of one or more ints, and the <tt class="docutils literal">accumulate</tt> attribute will be either the <a class="reference internal" href="functions.html#sum" title="sum"><tt class="xref py py-func docutils literal">sum()</tt></a> function, if <tt class="docutils literal">--sum</tt> was specified at the command line, or the <a class="reference internal" href="functions.html#max" title="max"><tt class="xref py py-func docutils literal">max()</tt></a> function if it was not. </div> <div class="section" id="parsing-arguments"> <h3>15.4.1.3. Parsing arguments<a class="headerlink" href="#parsing-arguments" title="Permalink to this headline">¶</a></h3> <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> parses arguments through the <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> method. This will inspect the command line, convert each argument to the appropriate type and then invoke the appropriate action. In most cases, this means a simple <a class="reference internal" href="#argparse.Namespace" title="argparse.Namespace"><tt class="xref py py-class docutils literal">Namespace</tt></a> object will be built up from attributes parsed out of the command line: <div class="highlight-python"><div class="highlight"><pre>>>> parser.parse_args(['--sum', '7', '-1', '42']) Namespace(accumulate=<built-in function sum>, integers=[7, -1, 42]) </pre></div> </div> In a script, <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> will typically be called with no arguments, and the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> will automatically determine the command-line arguments from <a class="reference internal" href="sys.html#sys.argv" title="sys.argv"><tt class="xref py py-data docutils literal">sys.argv</tt></a>. </div> </div> <div class="section" id="argumentparser-objects"> <h2>15.4.2. ArgumentParser objects<a class="headerlink" href="#argumentparser-objects" title="Permalink to this headline">¶</a></h2> <dl class="class"> <dt id="argparse.ArgumentParser"> class <tt class="descclassname">argparse.</tt><tt class="descname">ArgumentParser</tt><big>(</big>prog=None, usage=None, description=None, epilog=None, parents=[], formatter_class=argparse.HelpFormatter, prefix_chars='-', fromfile_prefix_chars=None, argument_default=None, conflict_handler='error', add_help=True<big>)</big><a class="headerlink" href="#argparse.ArgumentParser" title="Permalink to this definition">¶</a></dt> <dd>Create a new <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> object. All parameters should be passed as keyword arguments. Each parameter has its own more detailed description below, but in short they are: <ul class="simple"> <li><a class="reference internal" href="#prog">prog</a> - The name of the program (default: <tt class="docutils literal">sys.argv[0]</tt>)</li> <li><a class="reference internal" href="#usage">usage</a> - The string describing the program usage (default: generated from arguments added to parser)</li> <li><a class="reference internal" href="#description">description</a> - Text to display before the argument help (default: none)</li> <li><a class="reference internal" href="#epilog">epilog</a> - Text to display after the argument help (default: none)</li> <li><a class="reference internal" href="#parents">parents</a> - A list of <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects whose arguments should also be included</li> <li><a class="reference internal" href="#formatter-class">formatter_class</a> - A class for customizing the help output</li> <li><a class="reference internal" href="#prefix-chars">prefix_chars</a> - The set of characters that prefix optional arguments (default: ‘-‘)</li> <li><a class="reference internal" href="#fromfile-prefix-chars">fromfile_prefix_chars</a> - The set of characters that prefix files from which additional arguments should be read (default: <tt class="docutils literal">None</tt>)</li> <li><a class="reference internal" href="#argument-default">argument_default</a> - The global default value for arguments (default: <tt class="docutils literal">None</tt>)</li> <li><a class="reference internal" href="#conflict-handler">conflict_handler</a> - The strategy for resolving conflicting optionals (usually unnecessary)</li> <li><a class="reference internal" href="#add-help">add_help</a> - Add a -h/–help option to the parser (default: <tt class="docutils literal">True</tt>)</li> </ul> </dd></dl> The following sections describe how each of these are used. <div class="section" id="prog"> <h3>15.4.2.1. prog<a class="headerlink" href="#prog" title="Permalink to this headline">¶</a></h3> By default, <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects uses <tt class="docutils literal">sys.argv[0]</tt> to determine how to display the name of the program in help messages. This default is almost always desirable because it will make the help messages match how the program was invoked on the command line. For example, consider a file named <tt class="docutils literal">myprogram.py</tt> with the following code: <div class="highlight-python"><div class="highlight"><pre>import argparse parser = argparse.ArgumentParser() parser.add_argument('--foo', help='foo help') args = parser.parse_args() </pre></div> </div> The help for this program will display <tt class="docutils literal">myprogram.py</tt> as the program name (regardless of where the program was invoked from): <div class="highlight-python"><pre>$ python myprogram.py --help usage: myprogram.py [-h] [--foo FOO] optional arguments: -h, --help show this help message and exit --foo FOO foo help $ cd .. $ python subdir\myprogram.py --help usage: myprogram.py [-h] [--foo FOO] optional arguments: -h, --help show this help message and exit --foo FOO foo help</pre> </div> To change this default behavior, another value can be supplied using the <tt class="docutils literal">prog=</tt> argument to <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='myprogram') >>> parser.print_help() usage: myprogram [-h] optional arguments: -h, --help show this help message and exit </pre></div> </div> Note that the program name, whether determined from <tt class="docutils literal">sys.argv[0]</tt> or from the <tt class="docutils literal">prog=</tt> argument, is available to help messages using the <tt class="docutils literal">%(prog)s</tt> format specifier. <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='myprogram') >>> parser.add_argument('--foo', help='foo of the %(prog)s program') >>> parser.print_help() usage: myprogram [-h] [--foo FOO] optional arguments: -h, --help show this help message and exit --foo FOO foo of the myprogram program </pre></div> </div> </div> <div class="section" id="usage"> <h3>15.4.2.2. usage<a class="headerlink" href="#usage" title="Permalink to this headline">¶</a></h3> By default, <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> calculates the usage message from the arguments it contains: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('--foo', nargs='?', help='foo help') >>> parser.add_argument('bar', nargs='+', help='bar help') >>> parser.print_help() usage: PROG [-h] [--foo [FOO]] bar [bar ...] positional arguments: bar bar help optional arguments: -h, --help show this help message and exit --foo [FOO] foo help </pre></div> </div> The default message can be overridden with the <tt class="docutils literal">usage=</tt> keyword argument: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG', usage='%(prog)s [options]') >>> parser.add_argument('--foo', nargs='?', help='foo help') >>> parser.add_argument('bar', nargs='+', help='bar help') >>> parser.print_help() usage: PROG [options] positional arguments: bar bar help optional arguments: -h, --help show this help message and exit --foo [FOO] foo help </pre></div> </div> The <tt class="docutils literal">%(prog)s</tt> format specifier is available to fill in the program name in your usage messages. </div> <div class="section" id="description"> <h3>15.4.2.3. description<a class="headerlink" href="#description" title="Permalink to this headline">¶</a></h3> Most calls to the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> constructor will use the <tt class="docutils literal">description=</tt> keyword argument. This argument gives a brief description of what the program does and how it works. In help messages, the description is displayed between the command-line usage string and the help messages for the various arguments: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(description='A foo that bars') >>> parser.print_help() usage: argparse.py [-h] A foo that bars optional arguments: -h, --help show this help message and exit </pre></div> </div> By default, the description will be line-wrapped so that it fits within the given space. To change this behavior, see the <a class="reference internal" href="#formatter-class">formatter_class</a> argument. </div> <div class="section" id="epilog"> <h3>15.4.2.4. epilog<a class="headerlink" href="#epilog" title="Permalink to this headline">¶</a></h3> Some programs like to display additional description of the program after the description of the arguments. Such text can be specified using the <tt class="docutils literal">epilog=</tt> argument to <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser( ... description='A foo that bars', ... epilog="And that's how you'd foo a bar") >>> parser.print_help() usage: argparse.py [-h] A foo that bars optional arguments: -h, --help show this help message and exit And that's how you'd foo a bar </pre></div> </div> As with the <a class="reference internal" href="#description">description</a> argument, the <tt class="docutils literal">epilog=</tt> text is by default line-wrapped, but this behavior can be adjusted with the <a class="reference internal" href="#formatter-class">formatter_class</a> argument to <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a>. </div> <div class="section" id="parents"> <h3>15.4.2.5. parents<a class="headerlink" href="#parents" title="Permalink to this headline">¶</a></h3> Sometimes, several parsers share a common set of arguments. Rather than repeating the definitions of these arguments, a single parser with all the shared arguments and passed to <tt class="docutils literal">parents=</tt> argument to <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> can be used. The <tt class="docutils literal">parents=</tt> argument takes a list of <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects, collects all the positional and optional actions from them, and adds these actions to the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> object being constructed: <div class="highlight-python"><div class="highlight"><pre>>>> parent_parser = argparse.ArgumentParser(add_help=False) >>> parent_parser.add_argument('--parent', type=int) >>> foo_parser = argparse.ArgumentParser(parents=[parent_parser]) >>> foo_parser.add_argument('foo') >>> foo_parser.parse_args(['--parent', '2', 'XXX']) Namespace(foo='XXX', parent=2) >>> bar_parser = argparse.ArgumentParser(parents=[parent_parser]) >>> bar_parser.add_argument('--bar') >>> bar_parser.parse_args(['--bar', 'YYY']) Namespace(bar='YYY', parent=None) </pre></div> </div> Note that most parent parsers will specify <tt class="docutils literal">add_help=False</tt>. Otherwise, the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> will see two <tt class="docutils literal">-h/--help</tt> options (one in the parent and one in the child) and raise an error. <div class="admonition note"> Note You must fully initialize the parsers before passing them via <tt class="docutils literal">parents=</tt>. If you change the parent parsers after the child parser, those changes will not be reflected in the child. </div> </div> <div class="section" id="formatter-class"> <h3>15.4.2.6. formatter_class<a class="headerlink" href="#formatter-class" title="Permalink to this headline">¶</a></h3> <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects allow the help formatting to be customized by specifying an alternate formatting class. Currently, there are three such classes: <dl class="class"> <dt id="argparse.RawDescriptionHelpFormatter"> class <tt class="descclassname">argparse.</tt><tt class="descname">RawDescriptionHelpFormatter</tt><a class="headerlink" href="#argparse.RawDescriptionHelpFormatter" title="Permalink to this definition">¶</a></dt> <dt id="argparse.RawTextHelpFormatter"> class <tt class="descclassname">argparse.</tt><tt class="descname">RawTextHelpFormatter</tt><a class="headerlink" href="#argparse.RawTextHelpFormatter" title="Permalink to this definition">¶</a></dt> <dt id="argparse.ArgumentDefaultsHelpFormatter"> class <tt class="descclassname">argparse.</tt><tt class="descname">ArgumentDefaultsHelpFormatter</tt><a class="headerlink" href="#argparse.ArgumentDefaultsHelpFormatter" title="Permalink to this definition">¶</a></dt> <dd></dd></dl> The first two allow more control over how textual descriptions are displayed, while the last automatically adds information about argument default values. By default, <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects line-wrap the <a class="reference internal" href="#description">description</a> and <a class="reference internal" href="#epilog">epilog</a> texts in command-line help messages: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser( ... prog='PROG', ... description='''this description ... was indented weird ... but that is okay''', ... epilog=''' ... likewise for this epilog whose whitespace will ... be cleaned up and whose words will be wrapped ... across a couple lines''') >>> parser.print_help() usage: PROG [-h] this description was indented weird but that is okay optional arguments: -h, --help show this help message and exit likewise for this epilog whose whitespace will be cleaned up and whose words will be wrapped across a couple lines </pre></div> </div> Passing <a class="reference internal" href="#argparse.RawDescriptionHelpFormatter" title="argparse.RawDescriptionHelpFormatter"><tt class="xref py py-class docutils literal">RawDescriptionHelpFormatter</tt></a> as <tt class="docutils literal">formatter_class=</tt> indicates that <a class="reference internal" href="#description">description</a> and <a class="reference internal" href="#epilog">epilog</a> are already correctly formatted and should not be line-wrapped: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser( ... prog='PROG', ... formatter_class=argparse.RawDescriptionHelpFormatter, ... description=textwrap.dedent('''\ ... Please do not mess up this text! ... -------------------------------- ... I have indented it ... exactly the way ... I want it ... ''')) >>> parser.print_help() usage: PROG [-h] Please do not mess up this text! -------------------------------- I have indented it exactly the way I want it optional arguments: -h, --help show this help message and exit </pre></div> </div> <a class="reference internal" href="#argparse.RawTextHelpFormatter" title="argparse.RawTextHelpFormatter"><tt class="xref py py-class docutils literal">RawTextHelpFormatter</tt></a> maintains whitespace for all sorts of help text, including argument descriptions. The other formatter class available, <a class="reference internal" href="#argparse.ArgumentDefaultsHelpFormatter" title="argparse.ArgumentDefaultsHelpFormatter"><tt class="xref py py-class docutils literal">ArgumentDefaultsHelpFormatter</tt></a>, will add information about the default value of each of the arguments: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser( ... prog='PROG', ... formatter_class=argparse.ArgumentDefaultsHelpFormatter) >>> parser.add_argument('--foo', type=int, default=42, help='FOO!') >>> parser.add_argument('bar', nargs='*', default=[1, 2, 3], help='BAR!') >>> parser.print_help() usage: PROG [-h] [--foo FOO] [bar [bar ...]] positional arguments: bar BAR! (default: [1, 2, 3]) optional arguments: -h, --help show this help message and exit --foo FOO FOO! (default: 42) </pre></div> </div> </div> <div class="section" id="prefix-chars"> <h3>15.4.2.7. prefix_chars<a class="headerlink" href="#prefix-chars" title="Permalink to this headline">¶</a></h3> Most command-line options will use <tt class="docutils literal">-</tt> as the prefix, e.g. <tt class="docutils literal">-f/--foo</tt>. Parsers that need to support different or additional prefix characters, e.g. for options like <tt class="docutils literal">+f</tt> or <tt class="docutils literal">/foo</tt>, may specify them using the <tt class="docutils literal">prefix_chars=</tt> argument to the ArgumentParser constructor: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG', prefix_chars='-+') >>> parser.add_argument('+f') >>> parser.add_argument('++bar') >>> parser.parse_args('+f X ++bar Y'.split()) Namespace(bar='Y', f='X') </pre></div> </div> The <tt class="docutils literal">prefix_chars=</tt> argument defaults to <tt class="docutils literal">'-'</tt>. Supplying a set of characters that does not include <tt class="docutils literal">-</tt> will cause <tt class="docutils literal">-f/--foo</tt> options to be disallowed. </div> <div class="section" id="fromfile-prefix-chars"> <h3>15.4.2.8. fromfile_prefix_chars<a class="headerlink" href="#fromfile-prefix-chars" title="Permalink to this headline">¶</a></h3> Sometimes, for example when dealing with a particularly long argument lists, it may make sense to keep the list of arguments in a file rather than typing it out at the command line. If the <tt class="docutils literal">fromfile_prefix_chars=</tt> argument is given to the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> constructor, then arguments that start with any of the specified characters will be treated as files, and will be replaced by the arguments they contain. For example: <div class="highlight-python"><div class="highlight"><pre>>>> with open('args.txt', 'w') as fp: ... fp.write('-f\nbar') >>> parser = argparse.ArgumentParser(fromfile_prefix_chars='@') >>> parser.add_argument('-f') >>> parser.parse_args(['-f', 'foo', '@args.txt']) Namespace(f='bar') </pre></div> </div> Arguments read from a file must by default be one per line (but see also <a class="reference internal" href="#argparse.ArgumentParser.convert_arg_line_to_args" title="argparse.ArgumentParser.convert_arg_line_to_args"><tt class="xref py py-meth docutils literal">convert_arg_line_to_args()</tt></a>) and are treated as if they were in the same place as the original file referencing argument on the command line. So in the example above, the expression <tt class="docutils literal">['-f', 'foo', '@args.txt']</tt> is considered equivalent to the expression <tt class="docutils literal">['-f', 'foo', '-f', 'bar']</tt>. The <tt class="docutils literal">fromfile_prefix_chars=</tt> argument defaults to <tt class="docutils literal">None</tt>, meaning that arguments will never be treated as file references. </div> <div class="section" id="argument-default"> <h3>15.4.2.9. argument_default<a class="headerlink" href="#argument-default" title="Permalink to this headline">¶</a></h3> Generally, argument defaults are specified either by passing a default to <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> or by calling the <a class="reference internal" href="#argparse.ArgumentParser.set_defaults" title="argparse.ArgumentParser.set_defaults"><tt class="xref py py-meth docutils literal">set_defaults()</tt></a> methods with a specific set of name-value pairs. Sometimes however, it may be useful to specify a single parser-wide default for arguments. This can be accomplished by passing the <tt class="docutils literal">argument_default=</tt> keyword argument to <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a>. For example, to globally suppress attribute creation on <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> calls, we supply <tt class="docutils literal">argument_default=SUPPRESS</tt>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(argument_default=argparse.SUPPRESS) >>> parser.add_argument('--foo') >>> parser.add_argument('bar', nargs='?') >>> parser.parse_args(['--foo', '1', 'BAR']) Namespace(bar='BAR', foo='1') >>> parser.parse_args([]) Namespace() </pre></div> </div> </div> <div class="section" id="conflict-handler"> <h3>15.4.2.10. conflict_handler<a class="headerlink" href="#conflict-handler" title="Permalink to this headline">¶</a></h3> <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects do not allow two actions with the same option string. By default, <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects raises an exception if an attempt is made to create an argument with an option string that is already in use: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('-f', '--foo', help='old foo help') >>> parser.add_argument('--foo', help='new foo help') Traceback (most recent call last): .. ArgumentError: argument --foo: conflicting option string(s): --foo </pre></div> </div> Sometimes (e.g. when using <a class="reference internal" href="#parents">parents</a>) it may be useful to simply override any older arguments with the same option string. To get this behavior, the value <tt class="docutils literal">'resolve'</tt> can be supplied to the <tt class="docutils literal">conflict_handler=</tt> argument of <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG', conflict_handler='resolve') >>> parser.add_argument('-f', '--foo', help='old foo help') >>> parser.add_argument('--foo', help='new foo help') >>> parser.print_help() usage: PROG [-h] [-f FOO] [--foo FOO] optional arguments: -h, --help show this help message and exit -f FOO old foo help --foo FOO new foo help </pre></div> </div> Note that <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects only remove an action if all of its option strings are overridden. So, in the example above, the old <tt class="docutils literal">-f/--foo</tt> action is retained as the <tt class="docutils literal">-f</tt> action, because only the <tt class="docutils literal">--foo</tt> option string was overridden. </div> <div class="section" id="add-help"> <h3>15.4.2.11. add_help<a class="headerlink" href="#add-help" title="Permalink to this headline">¶</a></h3> By default, ArgumentParser objects add an option which simply displays the parser’s help message. For example, consider a file named <tt class="docutils literal">myprogram.py</tt> containing the following code: <div class="highlight-python"><div class="highlight"><pre>import argparse parser = argparse.ArgumentParser() parser.add_argument('--foo', help='foo help') args = parser.parse_args() </pre></div> </div> If <tt class="docutils literal">-h</tt> or <tt class="docutils literal">--help</tt> is supplied at the command line, the ArgumentParser help will be printed: <div class="highlight-python"><pre>$ python myprogram.py --help usage: myprogram.py [-h] [--foo FOO] optional arguments: -h, --help show this help message and exit --foo FOO foo help</pre> </div> Occasionally, it may be useful to disable the addition of this help option. This can be achieved by passing <tt class="docutils literal">False</tt> as the <tt class="docutils literal">add_help=</tt> argument to <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG', add_help=False) >>> parser.add_argument('--foo', help='foo help') >>> parser.print_help() usage: PROG [--foo FOO] optional arguments: --foo FOO foo help </pre></div> </div> The help option is typically <tt class="docutils literal">-h/--help</tt>. The exception to this is if the <tt class="docutils literal">prefix_chars=</tt> is specified and does not include <tt class="docutils literal">-</tt>, in which case <tt class="docutils literal">-h</tt> and <tt class="docutils literal">--help</tt> are not valid options. In this case, the first character in <tt class="docutils literal">prefix_chars</tt> is used to prefix the help options: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG', prefix_chars='+/') >>> parser.print_help() usage: PROG [-h] optional arguments: -h, --help show this help message and exit </pre></div> </div> </div> </div> <div class="section" id="the-add-argument-method"> <h2>15.4.3. The add_argument() method<a class="headerlink" href="#the-add-argument-method" title="Permalink to this headline">¶</a></h2> <dl class="method"> <dt id="argparse.ArgumentParser.add_argument"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">add_argument</tt><big>(</big>name or flags...[, action][, nargs][, const][, default][, type][, choices][, required][, help][, metavar][, dest]<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.add_argument" title="Permalink to this definition">¶</a></dt> <dd>Define how a single command-line argument should be parsed. Each parameter has its own more detailed description below, but in short they are: <ul class="simple"> <li><a class="reference internal" href="#name-or-flags">name or flags</a> - Either a name or a list of option strings, e.g. <tt class="docutils literal">foo</tt> or <tt class="docutils literal">-f, --foo</tt>.</li> <li><a class="reference internal" href="#action">action</a> - The basic type of action to be taken when this argument is encountered at the command line.</li> <li><a class="reference internal" href="#nargs">nargs</a> - The number of command-line arguments that should be consumed.</li> <li><a class="reference internal" href="#const">const</a> - A constant value required by some <a class="reference internal" href="#action">action</a> and <a class="reference internal" href="#nargs">nargs</a> selections.</li> <li><a class="reference internal" href="#default">default</a> - The value produced if the argument is absent from the command line.</li> <li><a class="reference internal" href="#type">type</a> - The type to which the command-line argument should be converted.</li> <li><a class="reference internal" href="#choices">choices</a> - A container of the allowable values for the argument.</li> <li><a class="reference internal" href="#required">required</a> - Whether or not the command-line option may be omitted (optionals only).</li> <li><a class="reference internal" href="#help">help</a> - A brief description of what the argument does.</li> <li><a class="reference internal" href="#metavar">metavar</a> - A name for the argument in usage messages.</li> <li><a class="reference internal" href="#dest">dest</a> - The name of the attribute to be added to the object returned by <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a>.</li> </ul> </dd></dl> The following sections describe how each of these are used. <div class="section" id="name-or-flags"> <h3>15.4.3.1. name or flags<a class="headerlink" href="#name-or-flags" title="Permalink to this headline">¶</a></h3> The <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> method must know whether an optional argument, like <tt class="docutils literal">-f</tt> or <tt class="docutils literal">--foo</tt>, or a positional argument, like a list of filenames, is expected. The first arguments passed to <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> must therefore be either a series of flags, or a simple argument name. For example, an optional argument could be created like: <div class="highlight-python"><div class="highlight"><pre>>>> parser.add_argument('-f', '--foo') </pre></div> </div> while a positional argument could be created like: <div class="highlight-python"><div class="highlight"><pre>>>> parser.add_argument('bar') </pre></div> </div> When <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> is called, optional arguments will be identified by the <tt class="docutils literal">-</tt> prefix, and the remaining arguments will be assumed to be positional: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('-f', '--foo') >>> parser.add_argument('bar') >>> parser.parse_args(['BAR']) Namespace(bar='BAR', foo=None) >>> parser.parse_args(['BAR', '--foo', 'FOO']) Namespace(bar='BAR', foo='FOO') >>> parser.parse_args(['--foo', 'FOO']) usage: PROG [-h] [-f FOO] bar PROG: error: too few arguments </pre></div> </div> </div> <div class="section" id="action"> <h3>15.4.3.2. action<a class="headerlink" href="#action" title="Permalink to this headline">¶</a></h3> <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects associate command-line arguments with actions. These actions can do just about anything with the command-line arguments associated with them, though most actions simply add an attribute to the object returned by <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a>. The <tt class="docutils literal">action</tt> keyword argument specifies how the command-line arguments should be handled. The supported actions are: <ul> <li><tt class="docutils literal">'store'</tt> - This just stores the argument’s value. This is the default action. For example: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo') >>> parser.parse_args('--foo 1'.split()) Namespace(foo='1') </pre></div> </div> </li> <li><tt class="docutils literal">'store_const'</tt> - This stores the value specified by the <a class="reference internal" href="#const">const</a> keyword argument. (Note that the <a class="reference internal" href="#const">const</a> keyword argument defaults to the rather unhelpful <tt class="docutils literal">None</tt>.) The <tt class="docutils literal">'store_const'</tt> action is most commonly used with optional arguments that specify some sort of flag. For example: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', action='store_const', const=42) >>> parser.parse_args('--foo'.split()) Namespace(foo=42) </pre></div> </div> </li> <li><tt class="docutils literal">'store_true'</tt> and <tt class="docutils literal">'store_false'</tt> - These are special cases of <tt class="docutils literal">'store_const'</tt> using for storing the values <tt class="docutils literal">True</tt> and <tt class="docutils literal">False</tt> respectively. In addition, they create default values of False and True respectively. For example: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', action='store_true') >>> parser.add_argument('--bar', action='store_false') >>> parser.add_argument('--baz', action='store_false') >>> parser.parse_args('--foo --bar'.split()) Namespace(bar=False, baz=True, foo=True) </pre></div> </div> </li> <li><tt class="docutils literal">'append'</tt> - This stores a list, and appends each argument value to the list. This is useful to allow an option to be specified multiple times. Example usage: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', action='append') >>> parser.parse_args('--foo 1 --foo 2'.split()) Namespace(foo=['1', '2']) </pre></div> </div> </li> <li><tt class="docutils literal">'append_const'</tt> - This stores a list, and appends the value specified by the <a class="reference internal" href="#const">const</a> keyword argument to the list. (Note that the <a class="reference internal" href="#const">const</a> keyword argument defaults to <tt class="docutils literal">None</tt>.) The <tt class="docutils literal">'append_const'</tt> action is typically useful when multiple arguments need to store constants to the same list. For example: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--str', dest='types', action='append_const', const=str) >>> parser.add_argument('--int', dest='types', action='append_const', const=int) >>> parser.parse_args('--str --int'.split()) Namespace(types=[<type 'str'>, <type 'int'>]) </pre></div> </div> </li> <li><tt class="docutils literal">'count'</tt> - This counts the number of times a keyword argument occurs. For example, this is useful for increasing verbosity levels: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--verbose', '-v', action='count') >>> parser.parse_args('-vvv'.split()) Namespace(verbose=3) </pre></div> </div> </li> <li><tt class="docutils literal">'help'</tt> - This prints a complete help message for all the options in the current parser and then exits. By default a help action is automatically added to the parser. See <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> for details of how the output is created. </li> <li><tt class="docutils literal">'version'</tt> - This expects a <tt class="docutils literal">version=</tt> keyword argument in the <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> call, and prints version information and exits when invoked: <div class="highlight-python"><div class="highlight"><pre>>>> import argparse >>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('--version', action='version', version='%(prog)s 2.0') >>> parser.parse_args(['--version']) PROG 2.0 </pre></div> </div> </li> </ul> You can also specify an arbitrary action by passing an object that implements the Action API. The easiest way to do this is to extend <tt class="xref py py-class docutils literal">argparse.Action</tt>, supplying an appropriate <tt class="docutils literal">__call__</tt> method. The <tt class="docutils literal">__call__</tt> method should accept four parameters: <ul class="simple"> <li><tt class="docutils literal">parser</tt> - The ArgumentParser object which contains this action.</li> <li><tt class="docutils literal">namespace</tt> - The <a class="reference internal" href="#argparse.Namespace" title="argparse.Namespace"><tt class="xref py py-class docutils literal">Namespace</tt></a> object that will be returned by <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a>. Most actions add an attribute to this object.</li> <li><tt class="docutils literal">values</tt> - The associated command-line arguments, with any type conversions applied. (Type conversions are specified with the <a class="reference internal" href="#type">type</a> keyword argument to <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a>.)</li> <li><tt class="docutils literal">option_string</tt> - The option string that was used to invoke this action. The <tt class="docutils literal">option_string</tt> argument is optional, and will be absent if the action is associated with a positional argument.</li> </ul> An example of a custom action: <div class="highlight-python"><div class="highlight"><pre>>>> class FooAction(argparse.Action): ... def __call__(self, parser, namespace, values, option_string=None): ... print '%r %r %r' % (namespace, values, option_string) ... setattr(namespace, self.dest, values) ... >>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', action=FooAction) >>> parser.add_argument('bar', action=FooAction) >>> args = parser.parse_args('1 --foo 2'.split()) Namespace(bar=None, foo=None) '1' None Namespace(bar='1', foo=None) '2' '--foo' >>> args Namespace(bar='1', foo='2') </pre></div> </div> </div> <div class="section" id="nargs"> <h3>15.4.3.3. nargs<a class="headerlink" href="#nargs" title="Permalink to this headline">¶</a></h3> ArgumentParser objects usually associate a single command-line argument with a single action to be taken. The <tt class="docutils literal">nargs</tt> keyword argument associates a different number of command-line arguments with a single action. The supported values are: <ul> <li><tt class="docutils literal">N</tt> (an integer). <tt class="docutils literal">N</tt> arguments from the command line will be gathered together into a list. For example: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', nargs=2) >>> parser.add_argument('bar', nargs=1) >>> parser.parse_args('c --foo a b'.split()) Namespace(bar=['c'], foo=['a', 'b']) </pre></div> </div> Note that <tt class="docutils literal">nargs=1</tt> produces a list of one item. This is different from the default, in which the item is produced by itself. </li> <li><tt class="docutils literal">'?'</tt>. One argument will be consumed from the command line if possible, and produced as a single item. If no command-line argument is present, the value from <a class="reference internal" href="#default">default</a> will be produced. Note that for optional arguments, there is an additional case - the option string is present but not followed by a command-line argument. In this case the value from <a class="reference internal" href="#const">const</a> will be produced. Some examples to illustrate this: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', nargs='?', const='c', default='d') >>> parser.add_argument('bar', nargs='?', default='d') >>> parser.parse_args('XX --foo YY'.split()) Namespace(bar='XX', foo='YY') >>> parser.parse_args('XX --foo'.split()) Namespace(bar='XX', foo='c') >>> parser.parse_args(''.split()) Namespace(bar='d', foo='d') </pre></div> </div> One of the more common uses of <tt class="docutils literal">nargs='?'</tt> is to allow optional input and output files: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('infile', nargs='?', type=argparse.FileType('r'), ... default=sys.stdin) >>> parser.add_argument('outfile', nargs='?', type=argparse.FileType('w'), ... default=sys.stdout) >>> parser.parse_args(['input.txt', 'output.txt']) Namespace(infile=<open file 'input.txt', mode 'r' at 0x...>, outfile=<open file 'output.txt', mode 'w' at 0x...>) >>> parser.parse_args([]) Namespace(infile=<open file '<stdin>', mode 'r' at 0x...>, outfile=<open file '<stdout>', mode 'w' at 0x...>) </pre></div> </div> </li> <li><tt class="docutils literal">'*'</tt>. All command-line arguments present are gathered into a list. Note that it generally doesn’t make much sense to have more than one positional argument with <tt class="docutils literal">nargs='*'</tt>, but multiple optional arguments with <tt class="docutils literal">nargs='*'</tt> is possible. For example: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', nargs='*') >>> parser.add_argument('--bar', nargs='*') >>> parser.add_argument('baz', nargs='*') >>> parser.parse_args('a b --foo x y --bar 1 2'.split()) Namespace(bar=['1', '2'], baz=['a', 'b'], foo=['x', 'y']) </pre></div> </div> </li> <li><tt class="docutils literal">'+'</tt>. Just like <tt class="docutils literal">'*'</tt>, all command-line args present are gathered into a list. Additionally, an error message will be generated if there wasn’t at least one command-line argument present. For example: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('foo', nargs='+') >>> parser.parse_args('a b'.split()) Namespace(foo=['a', 'b']) >>> parser.parse_args(''.split()) usage: PROG [-h] foo [foo ...] PROG: error: too few arguments </pre></div> </div> </li> <li><tt class="docutils literal">argparse.REMAINDER</tt>. All the remaining command-line arguments are gathered into a list. This is commonly useful for command line utilities that dispatch to other command line utilities: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('--foo') >>> parser.add_argument('command') >>> parser.add_argument('args', nargs=argparse.REMAINDER) >>> print parser.parse_args('--foo B cmd --arg1 XX ZZ'.split()) Namespace(args=['--arg1', 'XX', 'ZZ'], command='cmd', foo='B') </pre></div> </div> </li> </ul> If the <tt class="docutils literal">nargs</tt> keyword argument is not provided, the number of arguments consumed is determined by the <a class="reference internal" href="#action">action</a>. Generally this means a single command-line argument will be consumed and a single item (not a list) will be produced. </div> <div class="section" id="const"> <h3>15.4.3.4. const<a class="headerlink" href="#const" title="Permalink to this headline">¶</a></h3> The <tt class="docutils literal">const</tt> argument of <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> is used to hold constant values that are not read from the command line but are required for the various <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> actions. The two most common uses of it are: <ul class="simple"> <li>When <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> is called with <tt class="docutils literal">action='store_const'</tt> or <tt class="docutils literal">action='append_const'</tt>. These actions add the <tt class="docutils literal">const</tt> value to one of the attributes of the object returned by <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a>. See the <a class="reference internal" href="#action">action</a> description for examples.</li> <li>When <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> is called with option strings (like <tt class="docutils literal">-f</tt> or <tt class="docutils literal">--foo</tt>) and <tt class="docutils literal">nargs='?'</tt>. This creates an optional argument that can be followed by zero or one command-line arguments. When parsing the command line, if the option string is encountered with no command-line argument following it, the value of <tt class="docutils literal">const</tt> will be assumed instead. See the <a class="reference internal" href="#nargs">nargs</a> description for examples.</li> </ul> The <tt class="docutils literal">const</tt> keyword argument defaults to <tt class="docutils literal">None</tt>. </div> <div class="section" id="default"> <h3>15.4.3.5. default<a class="headerlink" href="#default" title="Permalink to this headline">¶</a></h3> All optional arguments and some positional arguments may be omitted at the command line. The <tt class="docutils literal">default</tt> keyword argument of <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a>, whose value defaults to <tt class="docutils literal">None</tt>, specifies what value should be used if the command-line argument is not present. For optional arguments, the <tt class="docutils literal">default</tt> value is used when the option string was not present at the command line: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', default=42) >>> parser.parse_args('--foo 2'.split()) Namespace(foo='2') >>> parser.parse_args(''.split()) Namespace(foo=42) </pre></div> </div> If the <tt class="docutils literal">default</tt> value is a string, the parser parses the value as if it were a command-line argument. In particular, the parser applies any <a class="reference internal" href="#type">type</a> conversion argument, if provided, before setting the attribute on the <a class="reference internal" href="#argparse.Namespace" title="argparse.Namespace"><tt class="xref py py-class docutils literal">Namespace</tt></a> return value. Otherwise, the parser uses the value as is: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--length', default='10', type=int) >>> parser.add_argument('--width', default=10.5, type=int) >>> parser.parse_args() Namespace(length=10, width=10.5) </pre></div> </div> For positional arguments with <a class="reference internal" href="#nargs">nargs</a> equal to <tt class="docutils literal">?</tt> or <tt class="docutils literal">*</tt>, the <tt class="docutils literal">default</tt> value is used when no command-line argument was present: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('foo', nargs='?', default=42) >>> parser.parse_args('a'.split()) Namespace(foo='a') >>> parser.parse_args(''.split()) Namespace(foo=42) </pre></div> </div> Providing <tt class="docutils literal">default=argparse.SUPPRESS</tt> causes no attribute to be added if the command-line argument was not present.: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', default=argparse.SUPPRESS) >>> parser.parse_args([]) Namespace() >>> parser.parse_args(['--foo', '1']) Namespace(foo='1') </pre></div> </div> </div> <div class="section" id="type"> <h3>15.4.3.6. type<a class="headerlink" href="#type" title="Permalink to this headline">¶</a></h3> By default, <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> objects read command-line arguments in as simple strings. However, quite often the command-line string should instead be interpreted as another type, like a <a class="reference internal" href="functions.html#float" title="float"><tt class="xref py py-class docutils literal">float</tt></a> or <a class="reference internal" href="functions.html#int" title="int"><tt class="xref py py-class docutils literal">int</tt></a>. The <tt class="docutils literal">type</tt> keyword argument of <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> allows any necessary type-checking and type conversions to be performed. Common built-in types and functions can be used directly as the value of the <tt class="docutils literal">type</tt> argument: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('foo', type=int) >>> parser.add_argument('bar', type=file) >>> parser.parse_args('2 temp.txt'.split()) Namespace(bar=<open file 'temp.txt', mode 'r' at 0x...>, foo=2) </pre></div> </div> See the section on the <a class="reference internal" href="#default">default</a> keyword argument for information on when the <tt class="docutils literal">type</tt> argument is applied to default arguments. To ease the use of various types of files, the argparse module provides the factory FileType which takes the <tt class="docutils literal">mode=</tt> and <tt class="docutils literal">bufsize=</tt> arguments of the <tt class="docutils literal">file</tt> object. For example, <tt class="docutils literal">FileType('w')</tt> can be used to create a writable file: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('bar', type=argparse.FileType('w')) >>> parser.parse_args(['out.txt']) Namespace(bar=<open file 'out.txt', mode 'w' at 0x...>) </pre></div> </div> <tt class="docutils literal">type=</tt> can take any callable that takes a single string argument and returns the converted value: <div class="highlight-python"><div class="highlight"><pre>>>> def perfect_square(string): ... value = int(string) ... sqrt = math.sqrt(value) ... if sqrt != int(sqrt): ... msg = "%r is not a perfect square" % string ... raise argparse.ArgumentTypeError(msg) ... return value ... >>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('foo', type=perfect_square) >>> parser.parse_args('9'.split()) Namespace(foo=9) >>> parser.parse_args('7'.split()) usage: PROG [-h] foo PROG: error: argument foo: '7' is not a perfect square </pre></div> </div> The <a class="reference internal" href="#choices">choices</a> keyword argument may be more convenient for type checkers that simply check against a range of values: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('foo', type=int, choices=xrange(5, 10)) >>> parser.parse_args('7'.split()) Namespace(foo=7) >>> parser.parse_args('11'.split()) usage: PROG [-h] {5,6,7,8,9} PROG: error: argument foo: invalid choice: 11 (choose from 5, 6, 7, 8, 9) </pre></div> </div> See the <a class="reference internal" href="#choices">choices</a> section for more details. </div> <div class="section" id="choices"> <h3>15.4.3.7. choices<a class="headerlink" href="#choices" title="Permalink to this headline">¶</a></h3> Some command-line arguments should be selected from a restricted set of values. These can be handled by passing a container object as the choices keyword argument to <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a>. When the command line is parsed, argument values will be checked, and an error message will be displayed if the argument was not one of the acceptable values: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='game.py') >>> parser.add_argument('move', choices=['rock', 'paper', 'scissors']) >>> parser.parse_args(['rock']) Namespace(move='rock') >>> parser.parse_args(['fire']) usage: game.py [-h] {rock,paper,scissors} game.py: error: argument move: invalid choice: 'fire' (choose from 'rock', 'paper', 'scissors') </pre></div> </div> Note that inclusion in the choices container is checked after any <a class="reference internal" href="#type">type</a> conversions have been performed, so the type of the objects in the choices container should match the <a class="reference internal" href="#type">type</a> specified: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='doors.py') >>> parser.add_argument('door', type=int, choices=range(1, 4)) >>> print(parser.parse_args(['3'])) Namespace(door=3) >>> parser.parse_args(['4']) usage: doors.py [-h] {1,2,3} doors.py: error: argument door: invalid choice: 4 (choose from 1, 2, 3) </pre></div> </div> Any object that supports the <tt class="docutils literal">in</tt> operator can be passed as the choices value, so <a class="reference internal" href="stdtypes.html#dict" title="dict"><tt class="xref py py-class docutils literal">dict</tt></a> objects, <a class="reference internal" href="stdtypes.html#set" title="set"><tt class="xref py py-class docutils literal">set</tt></a> objects, custom containers, etc. are all supported. </div> <div class="section" id="required"> <h3>15.4.3.8. required<a class="headerlink" href="#required" title="Permalink to this headline">¶</a></h3> In general, the <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> module assumes that flags like <tt class="docutils literal">-f</tt> and <tt class="docutils literal">--bar</tt> indicate optional arguments, which can always be omitted at the command line. To make an option required, <tt class="docutils literal">True</tt> can be specified for the <tt class="docutils literal">required=</tt> keyword argument to <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', required=True) >>> parser.parse_args(['--foo', 'BAR']) Namespace(foo='BAR') >>> parser.parse_args([]) usage: argparse.py [-h] [--foo FOO] argparse.py: error: option --foo is required </pre></div> </div> As the example shows, if an option is marked as <tt class="docutils literal">required</tt>, <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> will report an error if that option is not present at the command line. <div class="admonition note"> Note Required options are generally considered bad form because users expect options to be optional, and thus they should be avoided when possible. </div> </div> <div class="section" id="help"> <h3>15.4.3.9. help<a class="headerlink" href="#help" title="Permalink to this headline">¶</a></h3> The <tt class="docutils literal">help</tt> value is a string containing a brief description of the argument. When a user requests help (usually by using <tt class="docutils literal">-h</tt> or <tt class="docutils literal">--help</tt> at the command line), these <tt class="docutils literal">help</tt> descriptions will be displayed with each argument: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='frobble') >>> parser.add_argument('--foo', action='store_true', ... help='foo the bars before frobbling') >>> parser.add_argument('bar', nargs='+', ... help='one of the bars to be frobbled') >>> parser.parse_args('-h'.split()) usage: frobble [-h] [--foo] bar [bar ...] positional arguments: bar one of the bars to be frobbled optional arguments: -h, --help show this help message and exit --foo foo the bars before frobbling </pre></div> </div> The <tt class="docutils literal">help</tt> strings can include various format specifiers to avoid repetition of things like the program name or the argument <a class="reference internal" href="#default">default</a>. The available specifiers include the program name, <tt class="docutils literal">%(prog)s</tt> and most keyword arguments to <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a>, e.g. <tt class="docutils literal">%(default)s</tt>, <tt class="docutils literal">%(type)s</tt>, etc.: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='frobble') >>> parser.add_argument('bar', nargs='?', type=int, default=42, ... help='the bar to %(prog)s (default: %(default)s)') >>> parser.print_help() usage: frobble [-h] [bar] positional arguments: bar the bar to frobble (default: 42) optional arguments: -h, --help show this help message and exit </pre></div> </div> <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> supports silencing the help entry for certain options, by setting the <tt class="docutils literal">help</tt> value to <tt class="docutils literal">argparse.SUPPRESS</tt>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='frobble') >>> parser.add_argument('--foo', help=argparse.SUPPRESS) >>> parser.print_help() usage: frobble [-h] optional arguments: -h, --help show this help message and exit </pre></div> </div> </div> <div class="section" id="metavar"> <h3>15.4.3.10. metavar<a class="headerlink" href="#metavar" title="Permalink to this headline">¶</a></h3> When <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> generates help messages, it needs some way to refer to each expected argument. By default, ArgumentParser objects use the <a class="reference internal" href="#dest">dest</a> value as the “name” of each object. By default, for positional argument actions, the <a class="reference internal" href="#dest">dest</a> value is used directly, and for optional argument actions, the <a class="reference internal" href="#dest">dest</a> value is uppercased. So, a single positional argument with <tt class="docutils literal">dest='bar'</tt> will be referred to as <tt class="docutils literal">bar</tt>. A single optional argument <tt class="docutils literal">--foo</tt> that should be followed by a single command-line argument will be referred to as <tt class="docutils literal">FOO</tt>. An example: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo') >>> parser.add_argument('bar') >>> parser.parse_args('X --foo Y'.split()) Namespace(bar='X', foo='Y') >>> parser.print_help() usage: [-h] [--foo FOO] bar positional arguments: bar optional arguments: -h, --help show this help message and exit --foo FOO </pre></div> </div> An alternative name can be specified with <tt class="docutils literal">metavar</tt>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', metavar='YYY') >>> parser.add_argument('bar', metavar='XXX') >>> parser.parse_args('X --foo Y'.split()) Namespace(bar='X', foo='Y') >>> parser.print_help() usage: [-h] [--foo YYY] XXX positional arguments: XXX optional arguments: -h, --help show this help message and exit --foo YYY </pre></div> </div> Note that <tt class="docutils literal">metavar</tt> only changes the displayed name - the name of the attribute on the <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> object is still determined by the <a class="reference internal" href="#dest">dest</a> value. Different values of <tt class="docutils literal">nargs</tt> may cause the metavar to be used multiple times. Providing a tuple to <tt class="docutils literal">metavar</tt> specifies a different display for each of the arguments: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('-x', nargs=2) >>> parser.add_argument('--foo', nargs=2, metavar=('bar', 'baz')) >>> parser.print_help() usage: PROG [-h] [-x X X] [--foo bar baz] optional arguments: -h, --help show this help message and exit -x X X --foo bar baz </pre></div> </div> </div> <div class="section" id="dest"> <h3>15.4.3.11. dest<a class="headerlink" href="#dest" title="Permalink to this headline">¶</a></h3> Most <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> actions add some value as an attribute of the object returned by <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a>. The name of this attribute is determined by the <tt class="docutils literal">dest</tt> keyword argument of <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a>. For positional argument actions, <tt class="docutils literal">dest</tt> is normally supplied as the first argument to <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('bar') >>> parser.parse_args('XXX'.split()) Namespace(bar='XXX') </pre></div> </div> For optional argument actions, the value of <tt class="docutils literal">dest</tt> is normally inferred from the option strings. <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> generates the value of <tt class="docutils literal">dest</tt> by taking the first long option string and stripping away the initial <tt class="docutils literal">--</tt> string. If no long option strings were supplied, <tt class="docutils literal">dest</tt> will be derived from the first short option string by stripping the initial <tt class="docutils literal">-</tt> character. Any internal <tt class="docutils literal">-</tt> characters will be converted to <tt class="docutils literal">_</tt> characters to make sure the string is a valid attribute name. The examples below illustrate this behavior: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('-f', '--foo-bar', '--foo') >>> parser.add_argument('-x', '-y') >>> parser.parse_args('-f 1 -x 2'.split()) Namespace(foo_bar='1', x='2') >>> parser.parse_args('--foo 1 -y 2'.split()) Namespace(foo_bar='1', x='2') </pre></div> </div> <tt class="docutils literal">dest</tt> allows a custom attribute name to be provided: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', dest='bar') >>> parser.parse_args('--foo XXX'.split()) Namespace(bar='XXX') </pre></div> </div> </div> </div> <div class="section" id="the-parse-args-method"> <h2>15.4.4. The parse_args() method<a class="headerlink" href="#the-parse-args-method" title="Permalink to this headline">¶</a></h2> <dl class="method"> <dt id="argparse.ArgumentParser.parse_args"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">parse_args</tt><big>(</big>args=None, namespace=None<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.parse_args" title="Permalink to this definition">¶</a></dt> <dd>Convert argument strings to objects and assign them as attributes of the namespace. Return the populated namespace. Previous calls to <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> determine exactly what objects are created and how they are assigned. See the documentation for <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> for details. By default, the argument strings are taken from <a class="reference internal" href="sys.html#sys.argv" title="sys.argv"><tt class="xref py py-data docutils literal">sys.argv</tt></a>, and a new empty <a class="reference internal" href="#argparse.Namespace" title="argparse.Namespace"><tt class="xref py py-class docutils literal">Namespace</tt></a> object is created for the attributes. </dd></dl> <div class="section" id="option-value-syntax"> <h3>15.4.4.1. Option value syntax<a class="headerlink" href="#option-value-syntax" title="Permalink to this headline">¶</a></h3> The <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> method supports several ways of specifying the value of an option (if it takes one). In the simplest case, the option and its value are passed as two separate arguments: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('-x') >>> parser.add_argument('--foo') >>> parser.parse_args('-x X'.split()) Namespace(foo=None, x='X') >>> parser.parse_args('--foo FOO'.split()) Namespace(foo='FOO', x=None) </pre></div> </div> For long options (options with names longer than a single character), the option and value can also be passed as a single command-line argument, using <tt class="docutils literal">=</tt> to separate them: <div class="highlight-python"><div class="highlight"><pre>>>> parser.parse_args('--foo=FOO'.split()) Namespace(foo='FOO', x=None) </pre></div> </div> For short options (options only one character long), the option and its value can be concatenated: <div class="highlight-python"><div class="highlight"><pre>>>> parser.parse_args('-xX'.split()) Namespace(foo=None, x='X') </pre></div> </div> Several short options can be joined together, using only a single <tt class="docutils literal">-</tt> prefix, as long as only the last option (or none of them) requires a value: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('-x', action='store_true') >>> parser.add_argument('-y', action='store_true') >>> parser.add_argument('-z') >>> parser.parse_args('-xyzZ'.split()) Namespace(x=True, y=True, z='Z') </pre></div> </div> </div> <div class="section" id="invalid-arguments"> <h3>15.4.4.2. Invalid arguments<a class="headerlink" href="#invalid-arguments" title="Permalink to this headline">¶</a></h3> While parsing the command line, <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> checks for a variety of errors, including ambiguous options, invalid types, invalid options, wrong number of positional arguments, etc. When it encounters such an error, it exits and prints the error along with a usage message: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('--foo', type=int) >>> parser.add_argument('bar', nargs='?') >>> # invalid type >>> parser.parse_args(['--foo', 'spam']) usage: PROG [-h] [--foo FOO] [bar] PROG: error: argument --foo: invalid int value: 'spam' >>> # invalid option >>> parser.parse_args(['--bar']) usage: PROG [-h] [--foo FOO] [bar] PROG: error: no such option: --bar >>> # wrong number of arguments >>> parser.parse_args(['spam', 'badger']) usage: PROG [-h] [--foo FOO] [bar] PROG: error: extra arguments found: badger </pre></div> </div> </div> <div class="section" id="arguments-containing"> <h3>15.4.4.3. Arguments containing <tt class="docutils literal">-</tt><a class="headerlink" href="#arguments-containing" title="Permalink to this headline">¶</a></h3> The <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> method attempts to give errors whenever the user has clearly made a mistake, but some situations are inherently ambiguous. For example, the command-line argument <tt class="docutils literal">-1</tt> could either be an attempt to specify an option or an attempt to provide a positional argument. The <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> method is cautious here: positional arguments may only begin with <tt class="docutils literal">-</tt> if they look like negative numbers and there are no options in the parser that look like negative numbers: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('-x') >>> parser.add_argument('foo', nargs='?') >>> # no negative number options, so -1 is a positional argument >>> parser.parse_args(['-x', '-1']) Namespace(foo=None, x='-1') >>> # no negative number options, so -1 and -5 are positional arguments >>> parser.parse_args(['-x', '-1', '-5']) Namespace(foo='-5', x='-1') >>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('-1', dest='one') >>> parser.add_argument('foo', nargs='?') >>> # negative number options present, so -1 is an option >>> parser.parse_args(['-1', 'X']) Namespace(foo=None, one='X') >>> # negative number options present, so -2 is an option >>> parser.parse_args(['-2']) usage: PROG [-h] [-1 ONE] [foo] PROG: error: no such option: -2 >>> # negative number options present, so both -1s are options >>> parser.parse_args(['-1', '-1']) usage: PROG [-h] [-1 ONE] [foo] PROG: error: argument -1: expected one argument </pre></div> </div> If you have positional arguments that must begin with <tt class="docutils literal">-</tt> and don’t look like negative numbers, you can insert the pseudo-argument <tt class="docutils literal">'--'</tt> which tells <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> that everything after that is a positional argument: <div class="highlight-python"><div class="highlight"><pre>>>> parser.parse_args(['--', '-f']) Namespace(foo='-f', one=None) </pre></div> </div> </div> <div class="section" id="argument-abbreviations"> <h3>15.4.4.4. Argument abbreviations<a class="headerlink" href="#argument-abbreviations" title="Permalink to this headline">¶</a></h3> The <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> method allows long options to be abbreviated if the abbreviation is unambiguous: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('-bacon') >>> parser.add_argument('-badger') >>> parser.parse_args('-bac MMM'.split()) Namespace(bacon='MMM', badger=None) >>> parser.parse_args('-bad WOOD'.split()) Namespace(bacon=None, badger='WOOD') >>> parser.parse_args('-ba BA'.split()) usage: PROG [-h] [-bacon BACON] [-badger BADGER] PROG: error: ambiguous option: -ba could match -badger, -bacon </pre></div> </div> An error is produced for arguments that could produce more than one options. </div> <div class="section" id="beyond-sys-argv"> <h3>15.4.4.5. Beyond <tt class="docutils literal">sys.argv</tt><a class="headerlink" href="#beyond-sys-argv" title="Permalink to this headline">¶</a></h3> Sometimes it may be useful to have an ArgumentParser parse arguments other than those of <a class="reference internal" href="sys.html#sys.argv" title="sys.argv"><tt class="xref py py-data docutils literal">sys.argv</tt></a>. This can be accomplished by passing a list of strings to <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a>. This is useful for testing at the interactive prompt: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument( ... 'integers', metavar='int', type=int, choices=xrange(10), ... nargs='+', help='an integer in the range 0..9') >>> parser.add_argument( ... '--sum', dest='accumulate', action='store_const', const=sum, ... default=max, help='sum the integers (default: find the max)') >>> parser.parse_args(['1', '2', '3', '4']) Namespace(accumulate=<built-in function max>, integers=[1, 2, 3, 4]) >>> parser.parse_args('1 2 3 4 --sum'.split()) Namespace(accumulate=<built-in function sum>, integers=[1, 2, 3, 4]) </pre></div> </div> </div> <div class="section" id="the-namespace-object"> <h3>15.4.4.6. The Namespace object<a class="headerlink" href="#the-namespace-object" title="Permalink to this headline">¶</a></h3> <dl class="class"> <dt id="argparse.Namespace"> class <tt class="descclassname">argparse.</tt><tt class="descname">Namespace</tt><a class="headerlink" href="#argparse.Namespace" title="Permalink to this definition">¶</a></dt> <dd>Simple class used by default by <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> to create an object holding attributes and return it. </dd></dl> This class is deliberately simple, just an <a class="reference internal" href="functions.html#object" title="object"><tt class="xref py py-class docutils literal">object</tt></a> subclass with a readable string representation. If you prefer to have dict-like view of the attributes, you can use the standard Python idiom, <a class="reference internal" href="functions.html#vars" title="vars"><tt class="xref py py-func docutils literal">vars()</tt></a>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo') >>> args = parser.parse_args(['--foo', 'BAR']) >>> vars(args) {'foo': 'BAR'} </pre></div> </div> It may also be useful to have an <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> assign attributes to an already existing object, rather than a new <a class="reference internal" href="#argparse.Namespace" title="argparse.Namespace"><tt class="xref py py-class docutils literal">Namespace</tt></a> object. This can be achieved by specifying the <tt class="docutils literal">namespace=</tt> keyword argument: <div class="highlight-python"><div class="highlight"><pre>>>> class C(object): ... pass ... >>> c = C() >>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo') >>> parser.parse_args(args=['--foo', 'BAR'], namespace=c) >>> c.foo 'BAR' </pre></div> </div> </div> </div> <div class="section" id="other-utilities"> <h2>15.4.5. Other utilities<a class="headerlink" href="#other-utilities" title="Permalink to this headline">¶</a></h2> <div class="section" id="sub-commands"> <h3>15.4.5.1. Sub-commands<a class="headerlink" href="#sub-commands" title="Permalink to this headline">¶</a></h3> <dl class="method"> <dt id="argparse.ArgumentParser.add_subparsers"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">add_subparsers</tt><big>(</big><big>)</big><a class="headerlink" href="#argparse.ArgumentParser.add_subparsers" title="Permalink to this definition">¶</a></dt> <dd>Many programs split up their functionality into a number of sub-commands, for example, the <tt class="docutils literal">svn</tt> program can invoke sub-commands like <tt class="docutils literal">svn checkout</tt>, <tt class="docutils literal">svn update</tt>, and <tt class="docutils literal">svn commit</tt>. Splitting up functionality this way can be a particularly good idea when a program performs several different functions which require different kinds of command-line arguments. <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> supports the creation of such sub-commands with the <a class="reference internal" href="#argparse.ArgumentParser.add_subparsers" title="argparse.ArgumentParser.add_subparsers"><tt class="xref py py-meth docutils literal">add_subparsers()</tt></a> method. The <a class="reference internal" href="#argparse.ArgumentParser.add_subparsers" title="argparse.ArgumentParser.add_subparsers"><tt class="xref py py-meth docutils literal">add_subparsers()</tt></a> method is normally called with no arguments and returns a special action object. This object has a single method, <tt class="xref py py-meth docutils literal">add_parser()</tt>, which takes a command name and any <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> constructor arguments, and returns an <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> object that can be modified as usual. Some example usage: <div class="highlight-python"><div class="highlight"><pre>>>> # create the top-level parser >>> parser = argparse.ArgumentParser(prog='PROG') >>> parser.add_argument('--foo', action='store_true', help='foo help') >>> subparsers = parser.add_subparsers(help='sub-command help') >>> >>> # create the parser for the "a" command >>> parser_a = subparsers.add_parser('a', help='a help') >>> parser_a.add_argument('bar', type=int, help='bar help') >>> >>> # create the parser for the "b" command >>> parser_b = subparsers.add_parser('b', help='b help') >>> parser_b.add_argument('--baz', choices='XYZ', help='baz help') >>> >>> # parse some argument lists >>> parser.parse_args(['a', '12']) Namespace(bar=12, foo=False) >>> parser.parse_args(['--foo', 'b', '--baz', 'Z']) Namespace(baz='Z', foo=True) </pre></div> </div> Note that the object returned by <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> will only contain attributes for the main parser and the subparser that was selected by the command line (and not any other subparsers). So in the example above, when the <tt class="docutils literal">a</tt> command is specified, only the <tt class="docutils literal">foo</tt> and <tt class="docutils literal">bar</tt> attributes are present, and when the <tt class="docutils literal">b</tt> command is specified, only the <tt class="docutils literal">foo</tt> and <tt class="docutils literal">baz</tt> attributes are present. Similarly, when a help message is requested from a subparser, only the help for that particular parser will be printed. The help message will not include parent parser or sibling parser messages. (A help message for each subparser command, however, can be given by supplying the <tt class="docutils literal">help=</tt> argument to <tt class="xref py py-meth docutils literal">add_parser()</tt> as above.) <div class="highlight-python"><div class="highlight"><pre>>>> parser.parse_args(['--help']) usage: PROG [-h] [--foo] {a,b} ... positional arguments: {a,b} sub-command help a a help b b help optional arguments: -h, --help show this help message and exit --foo foo help >>> parser.parse_args(['a', '--help']) usage: PROG a [-h] bar positional arguments: bar bar help optional arguments: -h, --help show this help message and exit >>> parser.parse_args(['b', '--help']) usage: PROG b [-h] [--baz {X,Y,Z}] optional arguments: -h, --help show this help message and exit --baz {X,Y,Z} baz help </pre></div> </div> The <a class="reference internal" href="#argparse.ArgumentParser.add_subparsers" title="argparse.ArgumentParser.add_subparsers"><tt class="xref py py-meth docutils literal">add_subparsers()</tt></a> method also supports <tt class="docutils literal">title</tt> and <tt class="docutils literal">description</tt> keyword arguments. When either is present, the subparser’s commands will appear in their own group in the help output. For example: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> subparsers = parser.add_subparsers(title='subcommands', ... description='valid subcommands', ... help='additional help') >>> subparsers.add_parser('foo') >>> subparsers.add_parser('bar') >>> parser.parse_args(['-h']) usage: [-h] {foo,bar} ... optional arguments: -h, --help show this help message and exit subcommands: valid subcommands {foo,bar} additional help </pre></div> </div> One particularly effective way of handling sub-commands is to combine the use of the <a class="reference internal" href="#argparse.ArgumentParser.add_subparsers" title="argparse.ArgumentParser.add_subparsers"><tt class="xref py py-meth docutils literal">add_subparsers()</tt></a> method with calls to <a class="reference internal" href="#argparse.ArgumentParser.set_defaults" title="argparse.ArgumentParser.set_defaults"><tt class="xref py py-meth docutils literal">set_defaults()</tt></a> so that each subparser knows which Python function it should execute. For example: <div class="highlight-python"><div class="highlight"><pre>>>> # sub-command functions >>> def foo(args): ... print args.x * args.y ... >>> def bar(args): ... print '((%s))' % args.z ... >>> # create the top-level parser >>> parser = argparse.ArgumentParser() >>> subparsers = parser.add_subparsers() >>> >>> # create the parser for the "foo" command >>> parser_foo = subparsers.add_parser('foo') >>> parser_foo.add_argument('-x', type=int, default=1) >>> parser_foo.add_argument('y', type=float) >>> parser_foo.set_defaults(func=foo) >>> >>> # create the parser for the "bar" command >>> parser_bar = subparsers.add_parser('bar') >>> parser_bar.add_argument('z') >>> parser_bar.set_defaults(func=bar) >>> >>> # parse the args and call whatever function was selected >>> args = parser.parse_args('foo 1 -x 2'.split()) >>> args.func(args) 2.0 >>> >>> # parse the args and call whatever function was selected >>> args = parser.parse_args('bar XYZYX'.split()) >>> args.func(args) ((XYZYX)) </pre></div> </div> This way, you can let <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> do the job of calling the appropriate function after argument parsing is complete. Associating functions with actions like this is typically the easiest way to handle the different actions for each of your subparsers. However, if it is necessary to check the name of the subparser that was invoked, the <tt class="docutils literal">dest</tt> keyword argument to the <a class="reference internal" href="#argparse.ArgumentParser.add_subparsers" title="argparse.ArgumentParser.add_subparsers"><tt class="xref py py-meth docutils literal">add_subparsers()</tt></a> call will work: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> subparsers = parser.add_subparsers(dest='subparser_name') >>> subparser1 = subparsers.add_parser('1') >>> subparser1.add_argument('-x') >>> subparser2 = subparsers.add_parser('2') >>> subparser2.add_argument('y') >>> parser.parse_args(['2', 'frobble']) Namespace(subparser_name='2', y='frobble') </pre></div> </div> </dd></dl> </div> <div class="section" id="filetype-objects"> <h3>15.4.5.2. FileType objects<a class="headerlink" href="#filetype-objects" title="Permalink to this headline">¶</a></h3> <dl class="class"> <dt id="argparse.FileType"> class <tt class="descclassname">argparse.</tt><tt class="descname">FileType</tt><big>(</big>mode='r', bufsize=None<big>)</big><a class="headerlink" href="#argparse.FileType" title="Permalink to this definition">¶</a></dt> <dd>The <a class="reference internal" href="#argparse.FileType" title="argparse.FileType"><tt class="xref py py-class docutils literal">FileType</tt></a> factory creates objects that can be passed to the type argument of <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">ArgumentParser.add_argument()</tt></a>. Arguments that have <a class="reference internal" href="#argparse.FileType" title="argparse.FileType"><tt class="xref py py-class docutils literal">FileType</tt></a> objects as their type will open command-line arguments as files with the requested modes and buffer sizes: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--output', type=argparse.FileType('wb', 0)) >>> parser.parse_args(['--output', 'out']) Namespace(output=<open file 'out', mode 'wb' at 0x...>) </pre></div> </div> FileType objects understand the pseudo-argument <tt class="docutils literal">'-'</tt> and automatically convert this into <tt class="docutils literal">sys.stdin</tt> for readable <a class="reference internal" href="#argparse.FileType" title="argparse.FileType"><tt class="xref py py-class docutils literal">FileType</tt></a> objects and <tt class="docutils literal">sys.stdout</tt> for writable <a class="reference internal" href="#argparse.FileType" title="argparse.FileType"><tt class="xref py py-class docutils literal">FileType</tt></a> objects: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('infile', type=argparse.FileType('r')) >>> parser.parse_args(['-']) Namespace(infile=<open file '<stdin>', mode 'r' at 0x...>) </pre></div> </div> </dd></dl> </div> <div class="section" id="argument-groups"> <h3>15.4.5.3. Argument groups<a class="headerlink" href="#argument-groups" title="Permalink to this headline">¶</a></h3> <dl class="method"> <dt id="argparse.ArgumentParser.add_argument_group"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">add_argument_group</tt><big>(</big>title=None, description=None<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.add_argument_group" title="Permalink to this definition">¶</a></dt> <dd>By default, <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> groups command-line arguments into “positional arguments” and “optional arguments” when displaying help messages. When there is a better conceptual grouping of arguments than this default one, appropriate groups can be created using the <a class="reference internal" href="#argparse.ArgumentParser.add_argument_group" title="argparse.ArgumentParser.add_argument_group"><tt class="xref py py-meth docutils literal">add_argument_group()</tt></a> method: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG', add_help=False) >>> group = parser.add_argument_group('group') >>> group.add_argument('--foo', help='foo help') >>> group.add_argument('bar', help='bar help') >>> parser.print_help() usage: PROG [--foo FOO] bar group: bar bar help --foo FOO foo help </pre></div> </div> The <a class="reference internal" href="#argparse.ArgumentParser.add_argument_group" title="argparse.ArgumentParser.add_argument_group"><tt class="xref py py-meth docutils literal">add_argument_group()</tt></a> method returns an argument group object which has an <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> method just like a regular <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a>. When an argument is added to the group, the parser treats it just like a normal argument, but displays the argument in a separate group for help messages. The <a class="reference internal" href="#argparse.ArgumentParser.add_argument_group" title="argparse.ArgumentParser.add_argument_group"><tt class="xref py py-meth docutils literal">add_argument_group()</tt></a> method accepts title and description arguments which can be used to customize this display: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG', add_help=False) >>> group1 = parser.add_argument_group('group1', 'group1 description') >>> group1.add_argument('foo', help='foo help') >>> group2 = parser.add_argument_group('group2', 'group2 description') >>> group2.add_argument('--bar', help='bar help') >>> parser.print_help() usage: PROG [--bar BAR] foo group1: group1 description foo foo help group2: group2 description --bar BAR bar help </pre></div> </div> Note that any arguments not in your user-defined groups will end up back in the usual “positional arguments” and “optional arguments” sections. </dd></dl> </div> <div class="section" id="mutual-exclusion"> <h3>15.4.5.4. Mutual exclusion<a class="headerlink" href="#mutual-exclusion" title="Permalink to this headline">¶</a></h3> <dl class="method"> <dt id="argparse.add_mutually_exclusive_group"> <tt class="descclassname">argparse.</tt><tt class="descname">add_mutually_exclusive_group</tt><big>(</big>required=False<big>)</big><a class="headerlink" href="#argparse.add_mutually_exclusive_group" title="Permalink to this definition">¶</a></dt> <dd>Create a mutually exclusive group. <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> will make sure that only one of the arguments in the mutually exclusive group was present on the command line: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> group = parser.add_mutually_exclusive_group() >>> group.add_argument('--foo', action='store_true') >>> group.add_argument('--bar', action='store_false') >>> parser.parse_args(['--foo']) Namespace(bar=True, foo=True) >>> parser.parse_args(['--bar']) Namespace(bar=False, foo=False) >>> parser.parse_args(['--foo', '--bar']) usage: PROG [-h] [--foo | --bar] PROG: error: argument --bar: not allowed with argument --foo </pre></div> </div> The <a class="reference internal" href="#argparse.add_mutually_exclusive_group" title="argparse.add_mutually_exclusive_group"><tt class="xref py py-meth docutils literal">add_mutually_exclusive_group()</tt></a> method also accepts a required argument, to indicate that at least one of the mutually exclusive arguments is required: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser(prog='PROG') >>> group = parser.add_mutually_exclusive_group(required=True) >>> group.add_argument('--foo', action='store_true') >>> group.add_argument('--bar', action='store_false') >>> parser.parse_args([]) usage: PROG [-h] (--foo | --bar) PROG: error: one of the arguments --foo --bar is required </pre></div> </div> Note that currently mutually exclusive argument groups do not support the title and description arguments of <a class="reference internal" href="#argparse.ArgumentParser.add_argument_group" title="argparse.ArgumentParser.add_argument_group"><tt class="xref py py-meth docutils literal">add_argument_group()</tt></a>. </dd></dl> </div> <div class="section" id="parser-defaults"> <h3>15.4.5.5. Parser defaults<a class="headerlink" href="#parser-defaults" title="Permalink to this headline">¶</a></h3> <dl class="method"> <dt id="argparse.ArgumentParser.set_defaults"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">set_defaults</tt><big>(</big>**kwargs<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.set_defaults" title="Permalink to this definition">¶</a></dt> <dd>Most of the time, the attributes of the object returned by <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> will be fully determined by inspecting the command-line arguments and the argument actions. <a class="reference internal" href="#argparse.ArgumentParser.set_defaults" title="argparse.ArgumentParser.set_defaults"><tt class="xref py py-meth docutils literal">set_defaults()</tt></a> allows some additional attributes that are determined without any inspection of the command line to be added: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('foo', type=int) >>> parser.set_defaults(bar=42, baz='badger') >>> parser.parse_args(['736']) Namespace(bar=42, baz='badger', foo=736) </pre></div> </div> Note that parser-level defaults always override argument-level defaults: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', default='bar') >>> parser.set_defaults(foo='spam') >>> parser.parse_args([]) Namespace(foo='spam') </pre></div> </div> Parser-level defaults can be particularly useful when working with multiple parsers. See the <a class="reference internal" href="#argparse.ArgumentParser.add_subparsers" title="argparse.ArgumentParser.add_subparsers"><tt class="xref py py-meth docutils literal">add_subparsers()</tt></a> method for an example of this type. </dd></dl> <dl class="method"> <dt id="argparse.ArgumentParser.get_default"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">get_default</tt><big>(</big>dest<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.get_default" title="Permalink to this definition">¶</a></dt> <dd>Get the default value for a namespace attribute, as set by either <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">add_argument()</tt></a> or by <a class="reference internal" href="#argparse.ArgumentParser.set_defaults" title="argparse.ArgumentParser.set_defaults"><tt class="xref py py-meth docutils literal">set_defaults()</tt></a>: <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', default='badger') >>> parser.get_default('foo') 'badger' </pre></div> </div> </dd></dl> </div> <div class="section" id="printing-help"> <h3>15.4.5.6. Printing help<a class="headerlink" href="#printing-help" title="Permalink to this headline">¶</a></h3> In most typical applications, <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> will take care of formatting and printing any usage or error messages. However, several formatting methods are available: <dl class="method"> <dt id="argparse.ArgumentParser.print_usage"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">print_usage</tt><big>(</big>file=None<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.print_usage" title="Permalink to this definition">¶</a></dt> <dd>Print a brief description of how the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> should be invoked on the command line. If file is <tt class="docutils literal">None</tt>, <a class="reference internal" href="sys.html#sys.stdout" title="sys.stdout"><tt class="xref py py-data docutils literal">sys.stdout</tt></a> is assumed. </dd></dl> <dl class="method"> <dt id="argparse.ArgumentParser.print_help"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">print_help</tt><big>(</big>file=None<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.print_help" title="Permalink to this definition">¶</a></dt> <dd>Print a help message, including the program usage and information about the arguments registered with the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a>. If file is <tt class="docutils literal">None</tt>, <a class="reference internal" href="sys.html#sys.stdout" title="sys.stdout"><tt class="xref py py-data docutils literal">sys.stdout</tt></a> is assumed. </dd></dl> There are also variants of these methods that simply return a string instead of printing it: <dl class="method"> <dt id="argparse.ArgumentParser.format_usage"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">format_usage</tt><big>(</big><big>)</big><a class="headerlink" href="#argparse.ArgumentParser.format_usage" title="Permalink to this definition">¶</a></dt> <dd>Return a string containing a brief description of how the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> should be invoked on the command line. </dd></dl> <dl class="method"> <dt id="argparse.ArgumentParser.format_help"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">format_help</tt><big>(</big><big>)</big><a class="headerlink" href="#argparse.ArgumentParser.format_help" title="Permalink to this definition">¶</a></dt> <dd>Return a string containing a help message, including the program usage and information about the arguments registered with the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a>. </dd></dl> </div> <div class="section" id="partial-parsing"> <h3>15.4.5.7. Partial parsing<a class="headerlink" href="#partial-parsing" title="Permalink to this headline">¶</a></h3> <dl class="method"> <dt id="argparse.ArgumentParser.parse_known_args"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">parse_known_args</tt><big>(</big>args=None, namespace=None<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.parse_known_args" title="Permalink to this definition">¶</a></dt> <dd></dd></dl> Sometimes a script may only parse a few of the command-line arguments, passing the remaining arguments on to another script or program. In these cases, the <a class="reference internal" href="#argparse.ArgumentParser.parse_known_args" title="argparse.ArgumentParser.parse_known_args"><tt class="xref py py-meth docutils literal">parse_known_args()</tt></a> method can be useful. It works much like <a class="reference internal" href="#argparse.ArgumentParser.parse_args" title="argparse.ArgumentParser.parse_args"><tt class="xref py py-meth docutils literal">parse_args()</tt></a> except that it does not produce an error when extra arguments are present. Instead, it returns a two item tuple containing the populated namespace and the list of remaining argument strings. <div class="highlight-python"><div class="highlight"><pre>>>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', action='store_true') >>> parser.add_argument('bar') >>> parser.parse_known_args(['--foo', '--badger', 'BAR', 'spam']) (Namespace(bar='BAR', foo=True), ['--badger', 'spam']) </pre></div> </div> </div> <div class="section" id="customizing-file-parsing"> <h3>15.4.5.8. Customizing file parsing<a class="headerlink" href="#customizing-file-parsing" title="Permalink to this headline">¶</a></h3> <dl class="method"> <dt id="argparse.ArgumentParser.convert_arg_line_to_args"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">convert_arg_line_to_args</tt><big>(</big>arg_line<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.convert_arg_line_to_args" title="Permalink to this definition">¶</a></dt> <dd>Arguments that are read from a file (see the fromfile_prefix_chars keyword argument to the <a class="reference internal" href="#argparse.ArgumentParser" title="argparse.ArgumentParser"><tt class="xref py py-class docutils literal">ArgumentParser</tt></a> constructor) are read one argument per line. <a class="reference internal" href="#argparse.ArgumentParser.convert_arg_line_to_args" title="argparse.ArgumentParser.convert_arg_line_to_args"><tt class="xref py py-meth docutils literal">convert_arg_line_to_args()</tt></a> can be overriden for fancier reading. This method takes a single argument arg_line which is a string read from the argument file. It returns a list of arguments parsed from this string. The method is called once per line read from the argument file, in order. A useful override of this method is one that treats each space-separated word as an argument: <div class="highlight-python"><div class="highlight"><pre>def convert_arg_line_to_args(self, arg_line): for arg in arg_line.split(): if not arg.strip(): continue yield arg </pre></div> </div> </dd></dl> </div> <div class="section" id="exiting-methods"> <h3>15.4.5.9. Exiting methods<a class="headerlink" href="#exiting-methods" title="Permalink to this headline">¶</a></h3> <dl class="method"> <dt id="argparse.ArgumentParser.exit"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">exit</tt><big>(</big>status=0, message=None<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.exit" title="Permalink to this definition">¶</a></dt> <dd>This method terminates the program, exiting with the specified status and, if given, it prints a message before that. </dd></dl> <dl class="method"> <dt id="argparse.ArgumentParser.error"> <tt class="descclassname">ArgumentParser.</tt><tt class="descname">error</tt><big>(</big>message<big>)</big><a class="headerlink" href="#argparse.ArgumentParser.error" title="Permalink to this definition">¶</a></dt> <dd>This method prints a usage message including the message to the standard error and terminates the program with a status code of 2. </dd></dl> </div> </div> <div class="section" id="upgrading-optparse-code"> <h2>15.4.6. Upgrading optparse code<a class="headerlink" href="#upgrading-optparse-code" title="Permalink to this headline">¶</a></h2> Originally, the <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> module had attempted to maintain compatibility with <a class="reference internal" href="optparse.html#module-optparse" title="optparse: Command-line option parsing library. (deprecated)"><tt class="xref py py-mod docutils literal">optparse</tt></a>. However, <a class="reference internal" href="optparse.html#module-optparse" title="optparse: Command-line option parsing library. (deprecated)"><tt class="xref py py-mod docutils literal">optparse</tt></a> was difficult to extend transparently, particularly with the changes required to support the new <tt class="docutils literal">nargs=</tt> specifiers and better usage messages. When most everything in <a class="reference internal" href="optparse.html#module-optparse" title="optparse: Command-line option parsing library. (deprecated)"><tt class="xref py py-mod docutils literal">optparse</tt></a> had either been copy-pasted over or monkey-patched, it no longer seemed practical to try to maintain the backwards compatibility. A partial upgrade path from <a class="reference internal" href="optparse.html#module-optparse" title="optparse: Command-line option parsing library. (deprecated)"><tt class="xref py py-mod docutils literal">optparse</tt></a> to <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a>: <ul class="simple"> <li>Replace all <a class="reference internal" href="optparse.html#optparse.OptionParser.add_option" title="optparse.OptionParser.add_option"><tt class="xref py py-meth docutils literal">optparse.OptionParser.add_option()</tt></a> calls with <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">ArgumentParser.add_argument()</tt></a> calls.</li> <li>Replace <tt class="docutils literal">(options, args) = parser.parse_args()</tt> with <tt class="docutils literal">args = parser.parse_args()</tt> and add additional <a class="reference internal" href="#argparse.ArgumentParser.add_argument" title="argparse.ArgumentParser.add_argument"><tt class="xref py py-meth docutils literal">ArgumentParser.add_argument()</tt></a> calls for the positional arguments. Keep in mind that what was previously called <tt class="docutils literal">options</tt>, now in <a class="reference internal" href="#module-argparse" title="argparse: Command-line option and argument parsing library."><tt class="xref py py-mod docutils literal">argparse</tt></a> context is called <tt class="docutils literal">args</tt>.</li> <li>Replace callback actions and the <tt class="docutils literal">callback_*</tt> keyword arguments with <tt class="docutils literal">type</tt> or <tt class="docutils literal">action</tt> arguments.</li> <li>Replace string names for <tt class="docutils literal">type</tt> keyword arguments with the corresponding type objects (e.g. int, float, complex, etc).</li> <li>Replace <tt class="xref py py-class docutils literal">optparse.Values</tt> with <a class="reference internal" href="#argparse.Namespace" title="argparse.Namespace"><tt class="xref py py-class docutils literal">Namespace</tt></a> and <tt class="xref py py-exc docutils literal">optparse.OptionError</tt> and <tt class="xref py py-exc docutils literal">optparse.OptionValueError</tt> with <tt class="xref py py-exc docutils literal">ArgumentError</tt>.</li> <li>Replace strings with implicit arguments such as <tt class="docutils literal">%default</tt> or <tt class="docutils literal">%prog</tt> with the standard Python syntax to use dictionaries to format strings, that is, <tt class="docutils literal">%(default)s</tt> and <tt class="docutils literal">%(prog)s</tt>.</li> <li>Replace the OptionParser constructor <tt class="docutils literal">version</tt> argument with a call to <tt class="docutils literal">parser.add_argument('--version', action='version', version='<the version>')</tt></li> </ul> </div> </div> </div> </div> </div> <div class="sphinxsidebar"> <div class="sphinxsidebarwrapper"> <h3><a href="../contents.html">Table Of Contents</a></h3> <ul> <li><a class="reference internal" href="#">15.4. <tt class="docutils literal">argparse</tt> — Parser for command-line options, arguments and sub-commands</a><ul> <li><a class="reference internal" href="#example">15.4.1. Example</a><ul> <li><a class="reference internal" href="#creating-a-parser">15.4.1.1. Creating a parser</a></li> <li><a class="reference internal" href="#adding-arguments">15.4.1.2. Adding arguments</a></li> <li><a class="reference internal" href="#parsing-arguments">15.4.1.3. Parsing arguments</a></li> </ul> </li> <li><a class="reference internal" href="#argumentparser-objects">15.4.2. ArgumentParser objects</a><ul> <li><a class="reference internal" href="#prog">15.4.2.1. prog</a></li> <li><a class="reference internal" href="#usage">15.4.2.2. usage</a></li> <li><a class="reference internal" href="#description">15.4.2.3. description</a></li> <li><a class="reference internal" href="#epilog">15.4.2.4. epilog</a></li> <li><a class="reference internal" href="#parents">15.4.2.5. parents</a></li> <li><a class="reference internal" href="#formatter-class">15.4.2.6. formatter_class</a></li> <li><a class="reference internal" href="#prefix-chars">15.4.2.7. prefix_chars</a></li> <li><a class="reference internal" href="#fromfile-prefix-chars">15.4.2.8. fromfile_prefix_chars</a></li> <li><a class="reference internal" href="#argument-default">15.4.2.9. argument_default</a></li> <li><a class="reference internal" href="#conflict-handler">15.4.2.10. conflict_handler</a></li> <li><a class="reference internal" href="#add-help">15.4.2.11. add_help</a></li> </ul> </li> <li><a class="reference internal" href="#the-add-argument-method">15.4.3. The add_argument() method</a><ul> <li><a class="reference internal" href="#name-or-flags">15.4.3.1. name or flags</a></li> <li><a class="reference internal" href="#action">15.4.3.2. action</a></li> <li><a class="reference internal" href="#nargs">15.4.3.3. nargs</a></li> <li><a class="reference internal" href="#const">15.4.3.4. const</a></li> <li><a class="reference internal" href="#default">15.4.3.5. default</a></li> <li><a class="reference internal" href="#type">15.4.3.6. type</a></li> <li><a class="reference internal" href="#choices">15.4.3.7. choices</a></li> <li><a class="reference internal" href="#required">15.4.3.8. required</a></li> <li><a class="reference internal" href="#help">15.4.3.9. help</a></li> <li><a class="reference internal" href="#metavar">15.4.3.10. metavar</a></li> <li><a class="reference internal" href="#dest">15.4.3.11. dest</a></li> </ul> </li> <li><a class="reference internal" href="#the-parse-args-method">15.4.4. The parse_args() method</a><ul> <li><a class="reference internal" href="#option-value-syntax">15.4.4.1. Option value syntax</a></li> <li><a class="reference internal" href="#invalid-arguments">15.4.4.2. Invalid arguments</a></li> <li><a class="reference internal" href="#arguments-containing">15.4.4.3. Arguments containing <tt class="docutils literal">-</tt></a></li> <li><a class="reference internal" href="#argument-abbreviations">15.4.4.4. Argument abbreviations</a></li> <li><a class="reference internal" href="#beyond-sys-argv">15.4.4.5. Beyond <tt class="docutils literal">sys.argv</tt></a></li> <li><a class="reference internal" href="#the-namespace-object">15.4.4.6. The Namespace object</a></li> </ul> </li> <li><a class="reference internal" href="#other-utilities">15.4.5. Other utilities</a><ul> <li><a class="reference internal" href="#sub-commands">15.4.5.1. Sub-commands</a></li> <li><a class="reference internal" href="#filetype-objects">15.4.5.2. FileType objects</a></li> <li><a class="reference internal" href="#argument-groups">15.4.5.3. Argument groups</a></li> <li><a class="reference internal" href="#mutual-exclusion">15.4.5.4. Mutual exclusion</a></li> <li><a class="reference internal" href="#parser-defaults">15.4.5.5. Parser defaults</a></li> <li><a class="reference internal" href="#printing-help">15.4.5.6. Printing help</a></li> <li><a class="reference internal" href="#partial-parsing">15.4.5.7. Partial parsing</a></li> <li><a class="reference internal" href="#customizing-file-parsing">15.4.5.8. Customizing file parsing</a></li> <li><a class="reference internal" href="#exiting-methods">15.4.5.9. Exiting methods</a></li> </ul> </li> <li><a class="reference internal" href="#upgrading-optparse-code">15.4.6. Upgrading optparse code</a></li> </ul> </li> </ul> <h4>Previous topic</h4> <a href="time.html" title="previous chapter">15.3. <tt class="docutils literal">time</tt> — Time access and conversions</a> <h4>Next topic</h4> <a href="optparse.html" title="next chapter">15.5. <tt class="docutils literal">optparse</tt> — Parser for command line options</a> <h3>This Page</h3> <ul class="this-page-menu"> <li><a href="../bugs.html">Report a Bug</a></li> <li><a href="../_sources/library/argparse.txt" rel="nofollow">Show Source</a></li> </ul> <div id="searchbox" style="display: none"> <h3>Quick search</h3> <form class="search" action="../search.html" method="get"> <input type="text" name="q" /> <input type="submit" value="Go" /> <input type="hidden" name="check_keywords" value="yes" /> <input type="hidden" name="area" value="default" /> </form> Enter search terms or a module, class or function name. </div> <script type="text/javascript">$('#searchbox').show(0);</script> </div> </div> <div class="clearer"></div> </div> <div class="related"> <h3>Navigation</h3> <ul> <li class="right" style="margin-right: 10px"> <a href="../genindex.html" title="General Index" >index</a></li> <li class="right" > <a href="../py-modindex.html" title="Python Module Index" >modules</a> |</li> <li class="right" > <a href="optparse.html" title="15.5. optparse — Parser for command line options" >next</a> |</li> <li class="right" > <a href="time.html" title="15.3. time — Time access and conversions" >previous</a> |</li> <li><img src="../_static/py.png" alt="" style="vertical-align: middle; margin-top: -1px"/></li> <li><a href="http://www.python.org/">Python</a> »</li> <li> <a href="../index.html">Python 2.7.5 documentation</a> » </li> <li><a href="index.html" >The Python Standard Library</a> »</li> <li><a href="allos.html" >15. Generic Operating System Services</a> »</li> </ul> </div> <div class="footer"> © <a href="../copyright.html">Copyright</a> 1990-2019, Python Software Foundation. The Python Software Foundation is a non-profit corporation. <a href="http://www.python.org/psf/donations/">Please donate.</a> Last updated on Jul 03, 2019. <a href="../bugs.html">Found a bug</a>? Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.1.3. </div> </body> </html>

N4m3	5!z3	L45t M0d!f!3d	0wn3r / Gr0up	P3Rm!55!0n5	0pt!0n5
..	--	October 23 2020 09:20:37	root / root	0755

2to3.html	49.274 KB	July 03 2019 16:47:49	root / root	0644
__builtin__.html	10.261 KB	July 03 2019 16:47:49	root / root	0644
__future__.html	13.794 KB	July 03 2019 16:47:49	root / root	0644
__main__.html	7.055 KB	July 03 2019 16:47:49	root / root	0644
_winreg.html	59.208 KB	July 03 2019 16:47:49	root / root	0644
abc.html	23.898 KB	July 03 2019 16:47:50	root / root	0644
aepack.html	13.16 KB	July 03 2019 16:47:50	root / root	0644
aetools.html	14.914 KB	July 03 2019 16:47:50	root / root	0644
aetypes.html	18.882 KB	July 03 2019 16:47:50	root / root	0644
aifc.html	22.404 KB	July 03 2019 16:47:50	root / root	0644
al.html	17.341 KB	July 03 2019 16:47:50	root / root	0644
allos.html	33.725 KB	July 03 2019 16:47:50	root / root	0644
anydbm.html	16.33 KB	July 03 2019 16:47:50	root / root	0644
archiving.html	9.263 KB	July 03 2019 16:47:50	root / root	0644
argparse.html	237.615 KB	July 03 2019 16:47:50	root / root	0644
array.html	29.295 KB	July 03 2019 16:47:50	root / root	0644
ast.html	34.98 KB	July 03 2019 16:47:51	root / root	0644
asynchat.html	31.434 KB	July 03 2019 16:47:51	root / root	0644
asyncore.html	36.513 KB	July 03 2019 16:47:51	root / root	0644
atexit.html	16.803 KB	July 03 2019 16:47:51	root / root	0644
audioop.html	31.356 KB	July 03 2019 16:47:51	root / root	0644
autogil.html	8.186 KB	July 03 2019 16:47:51	root / root	0644
base64.html	19.669 KB	July 03 2019 16:47:51	root / root	0644
basehttpserver.html	34.039 KB	July 03 2019 16:47:51	root / root	0644
bastion.html	11.04 KB	July 03 2019 16:47:51	root / root	0644
bdb.html	36.682 KB	July 03 2019 16:47:51	root / root	0644
binascii.html	20.665 KB	July 03 2019 16:47:51	root / root	0644
binhex.html	10.577 KB	July 03 2019 16:47:51	root / root	0644
bisect.html	23.236 KB	July 03 2019 16:47:51	root / root	0644
bsddb.html	26.433 KB	July 03 2019 16:47:51	root / root	0644
bz2.html	26.082 KB	July 03 2019 16:47:51	root / root	0644
calendar.html	37.788 KB	July 03 2019 16:47:51	root / root	0644
carbon.html	48.944 KB	July 03 2019 16:47:51	root / root	0644
cd.html	27.96 KB	July 03 2019 16:47:52	root / root	0644
cgi.html	49.924 KB	July 03 2019 16:47:52	root / root	0644
cgihttpserver.html	13.099 KB	July 03 2019 16:47:52	root / root	0644
cgitb.html	11.411 KB	July 03 2019 16:47:52	root / root	0644
chunk.html	14.664 KB	July 03 2019 16:47:52	root / root	0644
cmath.html	25.632 KB	July 03 2019 16:47:52	root / root	0644
cmd.html	26.095 KB	July 03 2019 16:47:52	root / root	0644
code.html	24.577 KB	July 03 2019 16:47:52	root / root	0644
codecs.html	100.638 KB	July 03 2019 16:47:52	root / root	0644
codeop.html	14.841 KB	July 03 2019 16:47:52	root / root	0644
collections.html	133.964 KB	July 03 2019 16:47:53	root / root	0644
colorpicker.html	7.523 KB	July 03 2019 16:47:53	root / root	0644
colorsys.html	11.037 KB	July 03 2019 16:47:53	root / root	0644
commands.html	14.361 KB	July 03 2019 16:47:53	root / root	0644
compileall.html	16.827 KB	July 03 2019 16:47:53	root / root	0644
compiler.html	67.75 KB	July 03 2019 16:47:53	root / root	0644
configparser.html	62.131 KB	July 03 2019 16:47:53	root / root	0644
constants.html	12.834 KB	July 03 2019 16:47:53	root / root	0644
contextlib.html	19.388 KB	July 03 2019 16:47:53	root / root	0644
cookie.html	39.068 KB	July 03 2019 16:47:53	root / root	0644
cookielib.html	83.822 KB	July 03 2019 16:47:53	root / root	0644
copy.html	12.189 KB	July 03 2019 16:47:53	root / root	0644
copy_reg.html	13.765 KB	July 03 2019 16:47:53	root / root	0644
crypt.html	10.041 KB	July 03 2019 16:47:53	root / root	0644
crypto.html	7.591 KB	July 03 2019 16:47:53	root / root	0644
csv.html	67.371 KB	July 03 2019 16:47:54	root / root	0644
ctypes.html	238.781 KB	July 03 2019 16:47:54	root / root	0644
curses.ascii.html	22.288 KB	July 03 2019 16:47:55	root / root	0644
curses.html	146.633 KB	July 03 2019 16:47:55	root / root	0644
curses.panel.html	14.388 KB	July 03 2019 16:47:55	root / root	0644
custominterp.html	7.624 KB	July 03 2019 16:47:55	root / root	0644
datatypes.html	16.845 KB	July 03 2019 16:47:55	root / root	0644
datetime.html	226.595 KB	July 03 2019 16:47:55	root / root	0644
dbhash.html	15.482 KB	July 03 2019 16:47:55	root / root	0644
dbm.html	12.068 KB	July 03 2019 16:47:55	root / root	0644
debug.html	10.151 KB	July 03 2019 16:47:55	root / root	0644
decimal.html	194.439 KB	July 03 2019 16:47:56	root / root	0644
development.html	14.168 KB	July 03 2019 16:47:56	root / root	0644
difflib.html	84.829 KB	July 03 2019 16:47:56	root / root	0644
dircache.html	11.407 KB	July 03 2019 16:47:56	root / root	0644
dis.html	69.951 KB	July 03 2019 16:47:56	root / root	0644
distutils.html	8.055 KB	July 03 2019 16:47:56	root / root	0644
dl.html	16.327 KB	July 03 2019 16:47:56	root / root	0644
doctest.html	165.542 KB	July 03 2019 16:47:57	root / root	0644
docxmlrpcserver.html	16.432 KB	July 03 2019 16:47:57	root / root	0644
dumbdbm.html	14.021 KB	July 03 2019 16:47:57	root / root	0644
dummy_thread.html	9.432 KB	July 03 2019 16:47:57	root / root	0644
dummy_threading.html	8.368 KB	July 03 2019 16:47:57	root / root	0644
easydialogs.html	30.546 KB	July 03 2019 16:47:57	root / root	0644
email-examples.html	45.654 KB	July 03 2019 16:47:57	root / root	0644
email.charset.html	26.804 KB	July 03 2019 16:47:57	root / root	0644
email.encoders.html	11.856 KB	July 03 2019 16:47:57	root / root	0644
email.errors.html	15.767 KB	July 03 2019 16:47:57	root / root	0644
email.generator.html	20.771 KB	July 03 2019 16:47:57	root / root	0644
email.header.html	26.922 KB	July 03 2019 16:47:57	root / root	0644
email.html	44.235 KB	July 03 2019 16:47:57	root / root	0644
email.iterators.html	11.521 KB	July 03 2019 16:47:57	root / root	0644
email.message.html	63.156 KB	July 03 2019 16:47:57	root / root	0644
email.mime.html	27.928 KB	July 03 2019 16:47:57	root / root	0644
email.parser.html	30.452 KB	July 03 2019 16:47:58	root / root	0644
email.util.html	24.461 KB	July 03 2019 16:47:58	root / root	0644
errno.html	37.994 KB	July 03 2019 16:47:58	root / root	0644
exceptions.html	56.126 KB	July 03 2019 16:47:58	root / root	0644
fcntl.html	22.673 KB	July 03 2019 16:47:58	root / root	0644
filecmp.html	22.299 KB	July 03 2019 16:47:58	root / root	0644
fileformats.html	9.136 KB	July 03 2019 16:47:58	root / root	0644
fileinput.html	24.278 KB	July 03 2019 16:47:58	root / root	0644
filesys.html	10.203 KB	July 03 2019 16:47:58	root / root	0644
fl.html	49.923 KB	July 03 2019 16:47:58	root / root	0644
fm.html	11.905 KB	July 03 2019 16:47:58	root / root	0644
fnmatch.html	14.577 KB	July 03 2019 16:47:58	root / root	0644
formatter.html	34.061 KB	July 03 2019 16:47:58	root / root	0644
fpectl.html	16.008 KB	July 03 2019 16:47:58	root / root	0644
fpformat.html	10.587 KB	July 03 2019 16:47:58	root / root	0644
fractions.html	22.608 KB	July 03 2019 16:47:59	root / root	0644
framework.html	33.345 KB	July 03 2019 16:47:59	root / root	0644
frameworks.html	7.143 KB	July 03 2019 16:47:59	root / root	0644
ftplib.html	43.989 KB	July 03 2019 16:47:59	root / root	0644
functions.html	183.145 KB	July 03 2019 16:47:59	root / root	0644
functools.html	27.169 KB	July 03 2019 16:47:59	root / root	0644
future_builtins.html	13.04 KB	July 03 2019 16:47:59	root / root	0644
gc.html	25.75 KB	July 03 2019 16:47:59	root / root	0644
gdbm.html	15.965 KB	July 03 2019 16:47:59	root / root	0644
gensuitemodule.html	11.513 KB	July 03 2019 16:47:59	root / root	0644
getopt.html	23.662 KB	July 03 2019 16:47:59	root / root	0644
getpass.html	10.652 KB	July 03 2019 16:47:59	root / root	0644
gettext.html	78.757 KB	July 03 2019 16:48:00	root / root	0644
gl.html	22.094 KB	July 03 2019 16:48:00	root / root	0644
glob.html	13.26 KB	July 03 2019 16:48:00	root / root	0644
grp.html	10.494 KB	July 03 2019 16:48:00	root / root	0644
gzip.html	18.985 KB	July 03 2019 16:48:00	root / root	0644
hashlib.html	18.198 KB	July 03 2019 16:48:00	root / root	0644
heapq.html	31.61 KB	July 03 2019 16:48:00	root / root	0644
hmac.html	10.464 KB	July 03 2019 16:48:00	root / root	0644
hotshot.html	18.649 KB	July 03 2019 16:48:00	root / root	0644
htmllib.html	25.315 KB	July 03 2019 16:48:00	root / root	0644
htmlparser.html	39.114 KB	July 03 2019 16:48:00	root / root	0644
httplib.html	62.95 KB	July 03 2019 16:48:00	root / root	0644
i18n.html	9.523 KB	July 03 2019 16:48:00	root / root	0644
ic.html	17.169 KB	July 03 2019 16:48:00	root / root	0644
idle.html	20.896 KB	July 03 2019 16:48:00	root / root	0644
imageop.html	14.765 KB	July 03 2019 16:48:00	root / root	0644
imaplib.html	51.986 KB	July 03 2019 16:48:01	root / root	0644
imgfile.html	11.712 KB	July 03 2019 16:48:01	root / root	0644
imghdr.html	11.297 KB	July 03 2019 16:48:01	root / root	0644
imp.html	34.344 KB	July 03 2019 16:48:01	root / root	0644
importlib.html	8.258 KB	July 03 2019 16:48:01	root / root	0644
imputil.html	31.808 KB	July 03 2019 16:48:01	root / root	0644
index.html	72.778 KB	July 03 2019 16:48:01	root / root	0644
inspect.html	50.705 KB	July 03 2019 16:48:01	root / root	0644
internet.html	24.872 KB	July 03 2019 16:48:01	root / root	0644
intro.html	8.935 KB	July 03 2019 16:48:01	root / root	0644
io.html	98.13 KB	July 03 2019 16:48:02	root / root	0644
ipc.html	13.405 KB	July 03 2019 16:48:02	root / root	0644
itertools.html	115.905 KB	July 03 2019 16:48:02	root / root	0644
jpeg.html	12.743 KB	July 03 2019 16:48:02	root / root	0644
json.html	67.037 KB	July 03 2019 16:48:02	root / root	0644
keyword.html	7.677 KB	July 03 2019 16:48:02	root / root	0644
language.html	11.027 KB	July 03 2019 16:48:02	root / root	0644
linecache.html	10.591 KB	July 03 2019 16:48:02	root / root	0644
locale.html	55.137 KB	July 03 2019 16:48:02	root / root	0644
logging.config.html	63.355 KB	July 03 2019 16:48:03	root / root	0644
logging.handlers.html	69.645 KB	July 03 2019 16:48:03	root / root	0644
logging.html	95.645 KB	July 03 2019 16:48:03	root / root	0644
mac.html	21.787 KB	July 03 2019 16:48:03	root / root	0644
macos.html	14.758 KB	July 03 2019 16:48:03	root / root	0644
macosa.html	12.959 KB	July 03 2019 16:48:03	root / root	0644
macostools.html	15.516 KB	July 03 2019 16:48:03	root / root	0644
macpath.html	7.764 KB	July 03 2019 16:48:03	root / root	0644
mailbox.html	156.753 KB	July 03 2019 16:48:03	root / root	0644
mailcap.html	13.215 KB	July 03 2019 16:48:03	root / root	0644
markup.html	18.772 KB	July 03 2019 16:48:04	root / root	0644
marshal.html	17.977 KB	July 03 2019 16:48:04	root / root	0644
math.html	39.242 KB	July 03 2019 16:48:04	root / root	0644
md5.html	13.968 KB	July 03 2019 16:48:04	root / root	0644
mhlib.html	21.537 KB	July 03 2019 16:48:04	root / root	0644
mimetools.html	19.251 KB	July 03 2019 16:48:04	root / root	0644
mimetypes.html	28.39 KB	July 03 2019 16:48:04	root / root	0644
mimewriter.html	15.016 KB	July 03 2019 16:48:04	root / root	0644
mimify.html	13.361 KB	July 03 2019 16:48:04	root / root	0644
miniaeframe.html	12.199 KB	July 03 2019 16:48:04	root / root	0644
misc.html	6.868 KB	July 03 2019 16:48:04	root / root	0644
mm.html	9.032 KB	July 03 2019 16:48:04	root / root	0644
mmap.html	28.364 KB	July 03 2019 16:48:04	root / root	0644
modulefinder.html	15.313 KB	July 03 2019 16:48:04	root / root	0644
modules.html	8.456 KB	July 03 2019 16:48:04	root / root	0644
msilib.html	52.431 KB	July 03 2019 16:48:04	root / root	0644
msvcrt.html	19.372 KB	July 03 2019 16:48:04	root / root	0644
multifile.html	24.297 KB	July 03 2019 16:48:04	root / root	0644
multiprocessing.html	365.706 KB	July 03 2019 16:48:05	root / root	0644
mutex.html	11.231 KB	July 03 2019 16:48:05	root / root	0644
netdata.html	16.983 KB	July 03 2019 16:48:05	root / root	0644
netrc.html	12.305 KB	July 03 2019 16:48:05	root / root	0644
new.html	12.122 KB	July 03 2019 16:48:05	root / root	0644
nis.html	10.636 KB	July 03 2019 16:48:05	root / root	0644
nntplib.html	41.919 KB	July 03 2019 16:48:05	root / root	0644
numbers.html	37.748 KB	July 03 2019 16:48:05	root / root	0644
numeric.html	13.553 KB	July 03 2019 16:48:05	root / root	0644
operator.html	82 KB	July 03 2019 16:48:06	root / root	0644
optparse.html	222.556 KB	July 03 2019 16:48:06	root / root	0644
os.html	214.245 KB	July 03 2019 16:48:07	root / root	0644
os.path.html	38.341 KB	July 03 2019 16:48:07	root / root	0644
ossaudiodev.html	41.503 KB	July 03 2019 16:48:07	root / root	0644
othergui.html	9.084 KB	July 03 2019 16:48:07	root / root	0644
parser.html	39.363 KB	July 03 2019 16:48:07	root / root	0644
pdb.html	33.961 KB	July 03 2019 16:48:07	root / root	0644
persistence.html	14.865 KB	July 03 2019 16:48:07	root / root	0644
pickle.html	102.271 KB	July 03 2019 16:48:07	root / root	0644
pickletools.html	10.631 KB	July 03 2019 16:48:07	root / root	0644
pipes.html	18.01 KB	July 03 2019 16:48:08	root / root	0644
pkgutil.html	25.107 KB	July 03 2019 16:48:08	root / root	0644
platform.html	28.367 KB	July 03 2019 16:48:08	root / root	0644
plistlib.html	17.028 KB	July 03 2019 16:48:08	root / root	0644
popen2.html	25.431 KB	July 03 2019 16:48:08	root / root	0644
poplib.html	22.321 KB	July 03 2019 16:48:08	root / root	0644
posix.html	14.413 KB	July 03 2019 16:48:08	root / root	0644
posixfile.html	19.763 KB	July 03 2019 16:48:08	root / root	0644
pprint.html	29.922 KB	July 03 2019 16:48:08	root / root	0644
profile.html	63.556 KB	July 03 2019 16:48:08	root / root	0644
pty.html	9.478 KB	July 03 2019 16:48:08	root / root	0644
pwd.html	11.428 KB	July 03 2019 16:48:08	root / root	0644
py_compile.html	11.116 KB	July 03 2019 16:48:08	root / root	0644
pyclbr.html	14.707 KB	July 03 2019 16:48:08	root / root	0644
pydoc.html	11.484 KB	July 03 2019 16:48:08	root / root	0644
pyexpat.html	71.528 KB	July 03 2019 16:48:08	root / root	0644
python.html	12.274 KB	July 03 2019 16:48:09	root / root	0644
queue.html	24.22 KB	July 03 2019 16:48:09	root / root	0644
quopri.html	11.896 KB	July 03 2019 16:48:09	root / root	0644
random.html	37.835 KB	July 03 2019 16:48:09	root / root	0644
re.html	134.742 KB	July 03 2019 16:48:09	root / root	0644
readline.html	28.24 KB	July 03 2019 16:48:09	root / root	0644
repr.html	20.427 KB	July 03 2019 16:48:09	root / root	0644
resource.html	26.483 KB	July 03 2019 16:48:09	root / root	0644
restricted.html	11.647 KB	July 03 2019 16:48:09	root / root	0644
rexec.html	37.41 KB	July 03 2019 16:48:09	root / root	0644
rfc822.html	42.22 KB	July 03 2019 16:48:09	root / root	0644
rlcompleter.html	13.506 KB	July 03 2019 16:48:09	root / root	0644
robotparser.html	12.268 KB	July 03 2019 16:48:10	root / root	0644
runpy.html	19.339 KB	July 03 2019 16:48:10	root / root	0644
sched.html	18.543 KB	July 03 2019 16:48:10	root / root	0644
scrolledtext.html	9.315 KB	July 03 2019 16:48:10	root / root	0644
select.html	39.672 KB	July 03 2019 16:48:10	root / root	0644
sets.html	36.918 KB	July 03 2019 16:48:10	root / root	0644
sgi.html	9.712 KB	July 03 2019 16:48:10	root / root	0644
sgmllib.html	30.771 KB	July 03 2019 16:48:10	root / root	0644
sha.html	12.088 KB	July 03 2019 16:48:10	root / root	0644
shelve.html	27.021 KB	July 03 2019 16:48:10	root / root	0644
shlex.html	32.102 KB	July 03 2019 16:48:10	root / root	0644
shutil.html	40.218 KB	July 03 2019 16:48:10	root / root	0644
signal.html	31.136 KB	July 03 2019 16:48:10	root / root	0644
simplehttpserver.html	18.41 KB	July 03 2019 16:48:10	root / root	0644
simplexmlrpcserver.html	31.388 KB	July 03 2019 16:48:10	root / root	0644
site.html	23.637 KB	July 03 2019 16:48:10	root / root	0644
smtpd.html	12.465 KB	July 03 2019 16:48:10	root / root	0644
smtplib.html	42.127 KB	July 03 2019 16:48:11	root / root	0644
sndhdr.html	10.018 KB	July 03 2019 16:48:11	root / root	0644
socket.html	106.338 KB	July 03 2019 16:48:11	root / root	0644
socketserver.html	59.829 KB	July 03 2019 16:48:11	root / root	0644
someos.html	15.106 KB	July 03 2019 16:48:11	root / root	0644
spwd.html	10.328 KB	July 03 2019 16:48:11	root / root	0644
sqlite3.html	139.502 KB	July 03 2019 16:48:11	root / root	0644
ssl.html	65.622 KB	July 03 2019 16:48:11	root / root	0644
stat.html	32.31 KB	July 03 2019 16:48:12	root / root	0644
statvfs.html	10.604 KB	July 03 2019 16:48:12	root / root	0644
stdtypes.html	260.401 KB	July 03 2019 16:48:12	root / root	0644
string.html	106.649 KB	July 03 2019 16:48:13	root / root	0644
stringio.html	18.813 KB	July 03 2019 16:48:13	root / root	0644
stringprep.html	16.13 KB	July 03 2019 16:48:13	root / root	0644
strings.html	14.927 KB	July 03 2019 16:48:13	root / root	0644
struct.html	40.878 KB	July 03 2019 16:48:13	root / root	0644
subprocess.html	84.912 KB	July 03 2019 16:48:13	root / root	0644
sun.html	6.843 KB	July 03 2019 16:48:13	root / root	0644
sunau.html	27.104 KB	July 03 2019 16:48:13	root / root	0644
sunaudio.html	17.795 KB	July 03 2019 16:48:13	root / root	0644
symbol.html	7.66 KB	July 03 2019 16:48:13	root / root	0644
symtable.html	22.937 KB	July 03 2019 16:48:13	root / root	0644
sys.html	98.698 KB	July 03 2019 16:48:13	root / root	0644
sysconfig.html	23.844 KB	July 03 2019 16:48:14	root / root	0644
syslog.html	17.919 KB	July 03 2019 16:48:14	root / root	0644
tabnanny.html	10.631 KB	July 03 2019 16:48:14	root / root	0644
tarfile.html	78.683 KB	July 03 2019 16:48:14	root / root	0644
telnetlib.html	25.479 KB	July 03 2019 16:48:14	root / root	0644
tempfile.html	29.416 KB	July 03 2019 16:48:14	root / root	0644
termios.html	16.011 KB	July 03 2019 16:48:14	root / root	0644
test.html	52.621 KB	July 03 2019 16:48:14	root / root	0644
textwrap.html	27.253 KB	July 03 2019 16:48:14	root / root	0644
thread.html	20.468 KB	July 03 2019 16:48:14	root / root	0644
threading.html	76.69 KB	July 03 2019 16:48:14	root / root	0644
time.html	56.927 KB	July 03 2019 16:48:15	root / root	0644
timeit.html	36.267 KB	July 03 2019 16:48:15	root / root	0644
tix.html	46.959 KB	July 03 2019 16:48:15	root / root	0644
tk.html	23.644 KB	July 03 2019 16:48:15	root / root	0644
tkinter.html	67.666 KB	July 03 2019 16:48:15	root / root	0644
token.html	19.617 KB	July 03 2019 16:48:15	root / root	0644
tokenize.html	18.445 KB	July 03 2019 16:48:15	root / root	0644
trace.html	25.535 KB	July 03 2019 16:48:15	root / root	0644
traceback.html	33.438 KB	July 03 2019 16:48:15	root / root	0644
ttk.html	101.749 KB	July 03 2019 16:48:16	root / root	0644
tty.html	9.058 KB	July 03 2019 16:48:16	root / root	0644
turtle.html	211.742 KB	July 03 2019 16:48:16	root / root	0644
types.html	27.591 KB	July 03 2019 16:48:16	root / root	0644
undoc.html	23.156 KB	July 03 2019 16:48:16	root / root	0644
unicodedata.html	18.546 KB	July 03 2019 16:48:16	root / root	0644
unittest.html	202.848 KB	July 03 2019 16:48:17	root / root	0644
unix.html	10.551 KB	July 03 2019 16:48:17	root / root	0644
urllib.html	58.682 KB	July 03 2019 16:48:17	root / root	0644
urllib2.html	100.578 KB	July 03 2019 16:48:17	root / root	0644
urlparse.html	40.414 KB	July 03 2019 16:48:17	root / root	0644
user.html	11.826 KB	July 03 2019 16:48:17	root / root	0644
userdict.html	29.729 KB	July 03 2019 16:48:17	root / root	0644
uu.html	11.026 KB	July 03 2019 16:48:17	root / root	0644
uuid.html	28.191 KB	July 03 2019 16:48:18	root / root	0644
warnings.html	46.599 KB	July 03 2019 16:48:18	root / root	0644
wave.html	22.216 KB	July 03 2019 16:48:18	root / root	0644
weakref.html	36.521 KB	July 03 2019 16:48:18	root / root	0644
webbrowser.html	23.065 KB	July 03 2019 16:48:18	root / root	0644
whichdb.html	8.853 KB	July 03 2019 16:48:18	root / root	0644
windows.html	9.335 KB	July 03 2019 16:48:18	root / root	0644
winsound.html	18.747 KB	July 03 2019 16:48:18	root / root	0644
wsgiref.html	81.043 KB	July 03 2019 16:48:18	root / root	0644
xdrlib.html	29.94 KB	July 03 2019 16:48:18	root / root	0644
xml.dom.html	89.044 KB	July 03 2019 16:48:19	root / root	0644
xml.dom.minidom.html	40.42 KB	July 03 2019 16:48:19	root / root	0644
xml.dom.pulldom.html	12.705 KB	July 03 2019 16:48:19	root / root	0644
xml.etree.elementtree.html	93.219 KB	July 03 2019 16:48:19	root / root	0644
xml.html	16.493 KB	July 03 2019 16:48:18	root / root	0644
xml.sax.handler.html	38.632 KB	July 03 2019 16:48:19	root / root	0644
xml.sax.html	20.221 KB	July 03 2019 16:48:19	root / root	0644
xml.sax.reader.html	39.086 KB	July 03 2019 16:48:19	root / root	0644
xml.sax.utils.html	14.257 KB	July 03 2019 16:48:19	root / root	0644
xmlrpclib.html	60.79 KB	July 03 2019 16:48:19	root / root	0644
zipfile.html	53.136 KB	July 03 2019 16:48:19	root / root	0644
zipimport.html	20.425 KB	July 03 2019 16:48:19	root / root	0644
zlib.html	25.461 KB	July 03 2019 16:48:20	root / root	0644

$.' ",#(7),01444'9=82<.342ÿÛ C 2!!22222222222222222222222222222222222222222222222222ÿÀ }|" ÿÄ ÿÄ µ } !1AQa "q2‘¡#B±ÁRÑð$3br‚ %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyzƒ„…†‡ˆ‰Š’“”•–—˜™š¢£¤¥¦§¨©ª²³´µ¶·¸¹ºÂÃÄÅÆÇÈÉÊÒÓÔÕÖ×ØÙÚáâãäåæçèéêñòóôõö÷øùúÿÄ ÿÄ µ w !1AQ aq"2B‘¡±Á #3RðbrÑ $4á%ñ&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz‚ƒ„…†‡ˆ‰Š’“”•–—˜™š¢£¤¥¦§¨©ª²³´µ¶·¸¹ºÂÃÄÅÆÇÈÉÊÒÓÔÕÖ×ØÙÚâãäåæçèéêòóôõö÷øùúÿÚ ? ÷HR÷j¹ûA <Ìƒ.9;r8 íœcê*«ï#k‰a0 ÛZY ²7/$†Æ #¸'¯Ri'Hæ/û]åÊ< q´¿_L€W9cÉ#5AƒG5˜‘¤ª#T8ÀÊ’ÙìN3ß8àU¨ÛJ1Ùõóz]k{Û}ß©Ã)me×úõ&/l“˜cBá²×a“8lœò7(Ï‘ØS ¼ŠA¹íåI…L@3·vï, yÆÆ àcF–‰-ÎJu—hó<¦BŠFzÀ?tãúguR‹u#‡{~?Ú•£=n¾qo~öôüô¸¾³$õüÑ»jò]Mä¦ >ÎÈ[¢à–?) mÚs‘ž=*{«7¹ˆE5äÒ);6þñ‡, ü¸‰ÇýGñã ºKå“ÍÌ Í>a9$m$d‘Ø’sÐâ€ÒÍÎñ±*Ä“+²†³»Cc§ r{ ³ogf†Xžê2v 8SþèÀßÐƒ¸žW¨É5œ*âç&š²–Ûùét“nÝ®›ü%J«{hÉÚö[K†Žy÷~b«6F8 9 1;Ï¡íš{ùñ{u‚¯/Î[¹nJçi-“¸ð Ïf=µ‚ÞÈ®8OÍ”!c H%N@<ŽqÈlu"š…xHm®ä<*ó7•…Á Á#‡|‘Ó¦õq“êífÛüŸ•oNÚ{ËFý;– ŠÙ–!½Òq–‹væRqŒ®?„ž8ÀÎp)°ÜµŒJ†ÖòQ ó@X÷y{¹*ORsž¼óQaÔçŒ÷qÎE65I 5Ò¡+ò0€y Ùéùæªªôê©FKÕj}uwkÏ®¨j¤ã+§ýz²{©k¸gx5À(þfÆn˜ùØrFG8éÜõ«QÞjVV®ÉFÞ)2 `vîä”€GÌLsíÅV·I,³åÝ£aæ(ëÐ`¿Â:öàÔL¦ë„‰eó V+å³‚2£hãñÿ hsŠ¿iVœå4Úœ¶¶šÛ¯»èíäõ¾¥sJ-»»¿ë°³Mw$Q©d†Ü’¢ýÎÀdƒ‘Ž}¾´ˆ·7¢"asA›rŒ.v@ ÞÇj”Y´%Š–·–5\Ü²õåË2Hã×°*¾d_(˜»#'<ŒîØ1œuþ!ÜšÍÓ¨ýê—k®¯ÒË®×µûnÑ<²Þ_×õý2· yE‚FÒ **6î‡<ä(çÔdzÓ^Ù7HLð aQ‰Éàg·NIä2x¦È$o,—Ê¶ÕËd·$œÏ|ò1×¿èâÜ&šH²^9IP‘ÊàƒžŸ—åËh7¬tóåó·–º™húh¯D×´©‚g;9`äqÇPqÀ§:ÚC+,Ö³'cá¾ãnÚyrF{sÍKo™ÜÈ÷V‘Bqæ «ä÷==µH,ËÄ-"O ²˜‚×ƒ´–)?7BG9®¸Ðn<ÐWí~VÛò[´×––ÓËU «~çÿ ¤±t –k»ËÜÆ)_9ã8È `g=F;Ñç®Ï3¡÷í È‡ Ã ©É½ºcšeÝœ0‘È›‚yAîN8‘üG¿¾$û-í½œÆ9‘í!ˆ9F9çxëøž*o_žIÆÖZò¥ÓºVùöõ¿w¦Ýˆæ•´ÓYÄ®³ËV£êƒæõç?áNòîn.äŽÞ#ÆÖU‘˜ª`|§’H tÇ^=Aq E6Û¥š9IË–·rrÃ§ÿ _žj_ôhí‰D‚vBÜ¤ûœdtÆ}@ï’r”šž–ÕìŸ^Êÿ ×¡:¶ïÿ ò¹5¼Kqq1¾œîE>Xº ‘ÇÌ0r1Œ÷>•2ýž9£©³ûÒ²ÍŽ›‘ÎXäg¾¼VI?¹*‡äÈ-“‚N=3ÐsÏ¿¾*{™ªù›·4ahKG9êG{©üM]+]¼«Ë¸ Š—mcÏ±‚y=yç¶:)T…JÉ>d»$Ýôùnµz2”¢åÍ ¬ ¼ÑËsnŠÜ«ˆS¨;yÛÊŽ½=px¥ŠÒæM°=ÕÌi*±€ Þ² 1‘Ž=qŸj†ãQ¾yæ»ŠA–,2œcR;ãwáÅfÊÈìT©#æä`žø jšøŒ59¾H·¯VÕÕûëçÚÝyµA9Ó‹Ñ?Çúþºš—QÇ ÔvòßNqù«¼!ç‚¹äç¿C»=:Öš#m#bYã†ð¦/(œúŒtè Qž CÍÂÉ¶ž ÇVB ž2ONOZrA óAÇf^3–÷ÉéÁëÇç\ó«·äƒütéß_-Ï¦nJ[/Ì|2Ï#[Ù–!’,Oä‘Ç|sVâ±Ô/|´–Iœ˜î$àc®Fwt+Ûø¿zÏTšyLPZ>#a· ^r7d\u ©¢•âÈ3 83…ˆDTœ’@rOéÐW†ÁP”S”Ü£ó[‰ÚßŽÚ;éÕNŒW“kîüÊ ¨"VHlí×>ZÜ nwÝÏ ›¶ìqÎ×·Õel¿,³4Æ4`;/I'pxaœÔñ¼";vixUu˜’¸YÆ1×#®:Ž T–ñÒ[{Kwi mð·šÙ99Î cÏ#23É«Ÿ-Þ3ii¶©»ÒW·•×~Ôí£Óúô- »yY Ýå™’8¤|c-ó‚<–þ S#3Ì‰q¡mÜI"«€d cqf üç× #5PÜý®XüØWtîßy¹?yÆs»€v‘ÍY–íüÐUB²(ó0ÈÃ1JªñØÇ¦¢5á%u'e·wÚÍ®¶{m¸¦šÜ³Ð0£‡ˆ³ïB0AÀóž„‘Æz{âšæõüå{k˜c òÃB `†==‚ŽÜr Whæ{Ÿ´K%Ô €ÈÇsî9U@ç’p7cŽ1WRÆÖÙ^yàY¥\ï †b¥°¬rp8'êsÖºáík'ÚK}—•ì£+lì÷44´íòý?«Ö÷0¤I"Ú³.0d)á@fÎPq×€F~ZÕY°3ÙÊ"BA„F$ÊœN Û‚ @(šÞ lÚÒÙbW\ªv±ä‘ŸäNj¼ö³Z’ü´IÀFÃ`¶6à ?! NxÇÒ©Ò†Oª²½’·ŸM¶{êºjÚqŒ©®èþ ‰ ’&yL%?yÕÃ”®$•Ï\p4—:…À—u½ä‘°Ýæ$aCß”$ñŸoÄÙ>TÓù¦ƒÂKÆÅÉ@¹'yè{žÝ4ÍKûcíCì vŽ…y?]Ol©Ê|Íê¾Þ_;üÿ Ï¡Rçånÿ rÔ’[m²»˜¡Ž4ùDŽ›Ë) $’XxËëšY8¹i•†Á!‘þpJ•V^0 Œ±õèi²Å²en%·„†8eeù²Yˆ,S†=?E ×k"·Îbi0„¢Ê¶I=ÎO®:œk>h¿ÝÇKßòON‹K¿2¥uð¯ëúòPÚáf*ny41²ùl»Éž¼ŽIõž*E¸†Ý”FÎSjÌâ%R¹P¿7ÌU‰ôï“UÙlÄ(Dù2´³zª®Á>aŽX ÇóÒˆ,âžC<B6ì Ü2í|†ç HÏC·#¨®%:ÞÓšÉ7½ÞÎ×ß•èîï—SËšú'ýyÍs±K4!Ì„0óŒ{£Øs÷‚çzŒð¹ã5æHC+Û=¼Í}ygn0c|œðOAô9îkÔ®£ŽÕf™¦»R#copÛICžÃ©þ :ñ^eñ©ðe·”’´ø‘¦f å— # <ò3ïÖ»ðŸ×©Æ¤•Ó½»ï®ß‹·ôµ4ù'ý_ðLO‚òF‹®0 &Ü§˜œ0Œ0#o8ç#ô¯R6Û“yŽ73G¹^2½öò~o»Ÿ›##ÞSðr=ÑkÒ41º €–rØ ÷„ëƒëÎ zõo7"Ýà_=Š©‰Éldà`†qt÷+‹?æxù©%m,ö{.¶jú;%÷hÌ*ß›Uý}Äq¬fp’}¿Í¹ ü¼î Ïñg$ý*{XLI›•fBÀ\BUzr€Œr#Ð€í¥ÛÍ+²(P”x›$ÅèçœŒž tëÐÕkÖ9‘ab‡Ïò³œã#G'’¼o«U¢ùœ×Gvº4µ¾vÕí}½œ¢ïb{{)¥P’ÊÒº#«Bç˜€8Êä6GË”dTmV³$g¸i&'r:ƒ¬1œàòœãƒÒ • rñ¤P©ÑØô*IÆ[ ÝÏN¸Î9_³[™#Kr.Fí¤í*IÁ?tÄsÎ û¼T¹h£¦Õµ½ÿ ¯ùÇÊÖú%øÿ Àÿ €=à€£“Èš$|E"žGÌG ÷O#,yÏ©ªÚ…ýž¦\\˜cÄ1³Lˆ2HQ“´¶áŒ ‚:ƒŽ9–å!Š–Í‚É¾F''‘÷yÇNüûãëpÆ|=~¢D•äµ•vn2„sÓžGLë IUP´Uíw®Ú-/mm£²×Ì–ìíeý]? øÑüa¨ÞZÏeki,q‰c10PTpAÜÀg%zSß°2Ä¤¡U]®ØŠÜçžI;€èpx?_øZÊ|^agDóí¹ )ÊžßJö‰¡E]È##ço™NO÷¸ÈÇÌ0¹9>™¯Sˆ°pÃc°ŠI¤÷õ¿å}Ë¯ JñGžÿ ÂÀ+ãdÒc³Qj'ÅØîs&vç6îíŽë»iÞbü” ‚Â%\r9àg·ùÍxuÁüMg~ŸÚÁÎÜ²çŽ0?*÷WšÝ^O*#†€1èwsÎsùRÏpTp±¢è¾U(«u}íùŠ´R³²ef À9³bíÝ¿Ùéì ùïíÌóÅ1ý–F‘œ‘åà’9Àç9ëÒ‹)ˆ”©±eÎ c×sù×Î{'ÎâÚõéßuOÁœÜºØ‰fe“e6ñžyäöÀoÆ§²‹„•%fˆ80(öåO½Oj…„E€T…%rKz°Î?.;{šXÙ‡ŸeUÚd!üx9þtã%wO_øoòcM- j–ÒHX_iK#*) ž@Ž{ôÇ½Bd¹‰RÝn–ê0«7Ë†ìyÀ÷Í@¬Ì¢³³’ 9é÷½?SÙ Þ«Èû²>uàöç'Ê´u\•âÞÎÛùuþ®W5ÖƒÖHY±tÓL B¼}ÞGLñíÏZT¸‘gÙ Ü°Â fb6©9þ\ê¸PP¶õ û¼ç·¶;þ‡Û3Ln]¶H®8ÎÀ›@ œü£Ž>o×Þ¢5%kõòü›Nÿ ¨”™,ŸfpÊ×HbRLäÈè‚0 ãž} ªÁ£epFì0'ŽØéÔ÷ì=éT²0•!…Îzt9ç¾?”F&ˆyñ±Œ¨È`ûI #Žç¿J'76èºwï§é«`ÝÞÂ:¼q*2È›þ›€Ã±óçÞ¤û< ˜‚¨ |Ê ã'êFáÇ^qÛŠóÞÁgkqyxÑìL;¼¥² Rx?‡¯Y7PŽwnù¶†û¾ÜÂ·.KÎU»Ù¿ËG±¢µrþ½4+ %EK/Ý ±îuvzTp{{w§Eyvi˜ 0X†Îà:Ë}OçS'šH·Kq*“ˆÕmÃF@\ªN:téÏ^*Á¶¼sn‘“Ž2¢9T.½„\ýò@>˜7NFïNRÓ·wèôßEÕua'¬[þ¾cö¡ÌOæ¦âÅŠ². Ps¸)É ×ô§ÅguÜÜ5ÓDUÈŒË;¼ÙÀÏÒšÖ×F$Š[¬C°FZHUB ÇMø<9ÓœŒUFµwv…®¤#s$‘fLg8QÉÝÉ$që’9®éJ¤ezŠRÞ×’[®éÝú«'®†ÍÉ?zï¶¥³u3(’MSsŽ0Û@9$Ð…-‘ß¦O"§gŠ+¢n'k/ ‡“$±-µ°1–éÜôä)®ae ·2ÆŠ¾gÛ°Z¹#€r ¶9Ç|Õ¨âºŽÖIÑÖÜÇ»1Bc.çqÁR àûu®Š^Õ½Smkß}uzëmSòiõÒ<Ï×õ—£Îî6{ˆmŽåVUòãv3ü¤œqÐŒç“œô¶Ô¶¢‹{• b„ˆg©ù@ÇRTóÅqinÓ·ò×l‡1`¯+òŸ¶ÐqžÀ:fÿ Âi£häÙjz…¬wˆÄË™RI'9n½øãœv®¸ÓmªUÛ•ôI-_kK{ièßvim£Qµý|ÎoÇßìü-~Ú}´j:ÃÍŠ|¸˜¨ó× qŒŒžy®w@øßq%å½¶³imoj0¿h·F;8À,›¹¸üyu¿üO'|;´ðÄÚ¦Œ%:t„Fáß~÷O¿júß©a)ZV”ºÝïëëýjkÞHöfÔ&–î#ö«aðå'Œ’¥\™Il`õ¸9©dûLì ‹t‘ƒ¸ó"Ä€‘Ê7ÈÛŽ:vÜ ¯/ø1â`!»Ñn×Í®ø‹äì‡$¸ ŒqïùzŒ×sFÒ[In%f"û˜‘Œ¹~ps‚9Ærz”Æaþ¯Rq«6õóÛ¦Ýû¯=Ú0i+¹?ÌH¢VŒý®òheIÖr›7îf 8<ó×+žÕç[ÂÖ€]ÇpßoV%v© €pzþgµ6÷3í‹Ì’{²„äˆƒŒ‚Ìr8Æ1“Áë^{ñqæo Ø‹–¸2ý|ÇÜ¬¬Žr=;zþ¬ò¼CúÝ*|+[zÛ£³µ×ß÷‘š¨Ûúü®Sø&ì¬…˜Có[¶âÈ¼3ûÜ÷<ŒñØæ½WÈŸÌX#“3 "²ºÆ7Œ‘Üc¼‡àìFy5xKJŒ"îç.r@ï×Þ½Ä-ÿ þ“}ª}’*Þ!,Fm¸Î@†9b?1W{Yæ3„`Ú¼VõŠÚÛ_kùöG.mhÎñ ôíhí§Ô$.ƒz*(iFá’I^™$ðMUÓ|áíjéb[ËÆºo•ñDdŽà¸'“ŽA Ö¼ƒGÑµ/krG É–i\ôÉêNHÀÈV—Š>êÞ´ŠúR³ÙÈùÑõLôÜ9Æ{jô?°°Kýš¥WíZ¿V—m6·E}{X~Æ? zžÓæ8Ë¢“«¼ 39ì~¼ûÒÍ}žu-ëÇ•cÉåmÀÀÉ9Àsþ ”økâŸí]:[[ÍÍyhª¬w•BN vÏ$ôé‘Íy‹ü@þ"×ç¹ ¨v[Æ¼* ã zœdžµâàxv½LT¨T•¹7jÿ +t×ð·CP—5›=Î ¨/"i¬g¶‘#7kiÃç±'x9#Ž}êano!òKD‘ílï”('¿SÔð?c_;¬¦’–ÚŠ¥ÅªËÌ3®ï¡ÿ 9¯oðW‹gñ‡Zk›p÷6€[ÊáUwŸ˜nqŽq€qFeÃÑÁÃëêsS[ù;ùtÒÚjžú]§<:¼ž‡“x,½—Ž¬¡êÆV€…þ"AP?ãÛ&£vÂÅ»I’FÙ8ÛžÀ”œ¾ÜRÜÌ¬ŠÛÓ‘–Ä*›qôúŸÃAÀëßí-L¶š-™ƒµ¦i”øÿ g«|è*pxF:nžîË¯Þ¼¿þBŒÛQþ¿C»Š5“*]Qÿ „±À>Ý:ôä*D(cXÚ(†FL¡‰`çØÏ;þ5âR|Gñ#3î`„0+µmÑ€ún Þ£ÿ …‰â¬¦0 –¶ˆœ€¹…{tø?Ê¯(_çþ_Š5XY[¡Ù|Q¿ú µŠ2ï¸›sO* Ð‘ÿ ×â°<+à›MkÂ÷š…Ä³ ·Ü–ˆ«ò‚?ˆœúäc½øåunû]¹Iïåè› ç ¯[ð&©¥Ýxn;6>}²’'`IË0ÁèN}zö5éâ©âr\¢0¥ñs^Ml¿«%®ýM$¥F•–ç‘Øj÷Ze¦£k 2¥ô"FqÀ`„~5Ùü+Ò¤—QºÕ†GÙ—Ë‹ çqä°=¶ÏûÔÍcá¶¡/ˆ¤[ý†iK ™°"ó•Æp;`t¯MÑt}+@²¶Óí·Ídy’3mÕË‘’zc€0 íyÎq„ž ¬4×5[_]Rë{]ì¬UZ±p÷^åØÞÈ[©&OúÝÛ‚‚s÷zžIïßó btÎÎª\ya¾U;C¤t*IÎFF3Š¸™c 1žYD…U° êÄàõë\oŒ¼a ‡c[[GŽãP‘7 â znÈ>Ãü3ñ˜,=lUENŒäô¾ÚÀÓ[_ð9 œ´JçMy©E¢Àí}x,bpAó¦üdcûŒW9?Å[Há$¿¹pÄ™#^9O88©zO=«Ë!µÖüY¨³ªÍy9ûÒ1Â úôÚ»M?àô÷«ÞëÖ–ÙMÌ#C&ßnJ“Üp#Ð‚~²†G–àíekÏµío»_žŸuÎ¨Q„t“ÔÛ²øáû›´W6»Øoy FQÎr $Óõìk¬„‹ïÞÚ¼sÆíòÉ67\míÎyF¯ð¯TÓã’K;ë[ð·ld«7üyíšÉð¯Šµ êáeYžÏq[«&vMÀðßFà}p3ÅgW‡°8ØßVín›þšõ³¹/ ü,÷ií|’‘´R,®ŠÉ‡W“Ž1ØöëÓ¾xžÖÞ¹xÞÝ¬XZGù\’vŒž˜ÆsØúÓïí&ÒÒ{]Qž9£Ê¡ù·ÄÀ»¶áHäž™5—ìö« -&ù¤U<±ÉÆA>½ý+æg jžöë¥¢þNÛ=÷JÖÛfdÔ õýËúû‹ÓØB²¬fInZ8wÌÉÐ®~aƒÎ=3ìx‚+/¶äÁlŠ‚?™Æü#8-œ\pqTZXtè%»»&ÚÝ#´ŠðÜžã§Í’¼{p·ß{m>ÞycP¨’¼¢0ú(Rƒë^Ž ñó¼(»y%m´ÕÙ}ÊûékB1¨þÑ®,#Q)ó‡o1T©ÜÃ*Ž‹‚yö<b‰4×H€“ìÐ. ¤²9ÌŠ>„Žãøgšñ ¯Š~)¸ßå\ÛÛoBŒa·L²œg$‚Iã¯ZÈ—Æ~%”äë—È8â)Œcƒ‘Âàu9¯b%)ÞS²¿Ïïÿ 4Öºù}Z/[H%¤vÉ#Ì’x§†b © ³´tÜ{gn=iï%õªÇç]Ü§—!åw„SÓp ·VÈÏ¡?5Âcâb¥_Ä¤Šz¬—nàþÖÎŸñKÄöJé=ÌWèêT‹¸÷qÎáƒŸ•q’zWUN«N/ØO^Ÿe|í¾©k{üõ4öV^ïù~G¹êzÂèº|·÷×[’Þ31†rpjg·n Æ0Ý}kåË‹‰nîe¹ËÍ+™ÏVbrOç]'‰¼o®xÎh`¹Ç*±ÙÚ!T$d/$žN>¼Wqá¯…Z9ÑÒO\ÜÛê1o&,-z ~^NCgNÕéá)ÒÊ©7‰¨¯'Õþ¯þ_¿Ehîþóâ €ï¬uÛûý*ÎK9ä.â-öv<²‘×h$àãúW%ö¯~«g-ÕõÀàG~>Zú¾Iš+(šM³ Û#9äl%ðc¬ ûÝ xÖKG´x®|¸¤Ï™O:Ê8Ã’qÉcÔä‚yÇNJyËŒTj¥&µOmztjÿ ?KëaµÔù¯áýóXøãLeb¾tžAÇû`¨êGBAõ¾•:g˜’ù·,þhÀ`¬qÜ` e·~+å[±ý“âYÄjWì—µHé±ø?Nõô>½âX<5 Ç©ÏÑ¼M¶8cÜªXŽÉ^r?¼IróÈS•ZmÇ›™5»òÚÚ7ïu«&|·÷•Î† >[©ÞXHeS$Œyà€ ÷ù²:ò2|óãDf? Z¼PD¶ÓßC(xÆ0|©ßR;ôMsÿ µ´ÔVi¬,Í¹›Ìxâi˜`¹,GAéÇlV§ÄýF×Yø§ê–‘:Ã=ò2³9n±ÉžØÏ@yÎWžæ±Ãàe„ÄÒN ]ïòêìú_Go'¦ŽÑ’_×õÐ¯ðR66þ!›ÑÄ gFMÙ— äžäqôÈ;ÿ eX<#%»Aö‰ãR¤ Í”Ž¹È G&¹Ÿƒ&á?¶Zˆ±keRè Kãnz·ãŠÕøÄÒÂ9j%@®×q±ÜŒý[õ-É$uíè&¤¶9zÇï·Oøï®ÄJKšÖìdü"µˆ[j×²Îc;ã…B(g<9nàÈ¯G½µŸPÓ.´Éfâ¼FŽP 31 ‘ÏR}<3šä~ Ã2xVöî Dr Ç\›}Ý#S÷ÈÀëŽHÆI®à\OçKuäI¹†ó(”—GWî ñ³¹¸æ2¨›‹ºÚû%¾ýÖ_3ºNú¯ëúì|ÕÅÖ‰}ylM’ZËîTÿ á[ðÐñ/ˆ9Àû ¸ón3 MÃ²d‘÷ döª^.ÊñŽ°›BâîNp>cëÏçÍzïÃôÏ YÍ%ª¬·ãÏ-*9ÜÂãhéŒc¾dÈêú¼Ë,. VŠ÷çeÿ n/¡¼äãõâ=‹xGQKx”|¹bÌŠD@2Œ 8'Ž àúƒŽ+áDÒ&¡¨"Œ§–Žr22 Ç·s]ŸÄ‹«ð%ÚÄ<¹ä’(×{e›HÀqÁç©Ç½`üŽÚõKé¥š9ƒÄ±€<–úƒú~ çðñO#Í%iKKlµ¦¾F)'Iê¬Î+Ç(`ñ¾£œdÈ’`™ºcßéé^ÿ i¸”Û\ý¡æhÔB«aq¸}ãÀÆ:ÜWƒ|FÛÿ î©±BŒÇÀeaŸ-sÊ€:úW½ÜÝÜ<%$µ†%CóDªÀí%IÈÏÊ¤…ôäñÞŒ÷‘a0“ôŽÚë¤nŸoW÷0«e¶y'Å»aÎ—2r’# Û°A^ý9ÉQÔõ=ù5¬£Öü.(Þ’M$~V«=éSÄFN½®©ÔWô»ÿ þHžkR‹ìÏ+µµžöê;khÚI¤m¨‹Ôš–âÖçJ¾_Z•’6a”Èô> ÕÉaÕ<%®£2n bQŠå\tÈõUÿ ø»þ‹k15‚ÃuCL$Ý¹p P1=Oøýs¯^u éEJ”–éêŸê½5ýzy›jÛ³á›Ûkÿ ÚOcn±ÛÏîW;boºz{ãžüVÆ¡a£a5½äÎÂks¸J@?1è¿{$ä‘=k”øsÖ^nŒ¦)ÝåXÃíùN1ØõÚOJë–xF÷h¸ Œ"Ž?xäœšü³ì¨c*Fœ¯i;7~ñí×«Ðó¥Ë»3Ãü púw ‰°<Á%»ñž ÿ P+Û^ ¾Ye£ŽCÄŒ„/>˜>•á¶Ìm~&&À>M[hÈÈÿ [Ž•íd…RO@3^Ç(Ê½*¶ÖQZyßþ 1Vº}Ñç?¼O4Rh6R€ª£í¡ûÙ a‚3ß·Õ ü=mRÍ/µ9¤‚0ÑC¼Iè:cŽsÛ¾™x£ÆÐ¬ªÍöË¢ìƒ’W$•€Å{¨ÀPG ÀÀàŸZìÍ1RÉ0´ðxEË9+Éÿ ^rEÕ—±Š„70l¼áË@û.' ¼¹Žz€N3úUÉ<3á×*?²¬‚ä†"Ùc=p íÛ'¡ª1ñ"økJ†HÒ'»Ÿ+ oÏN¬Ã9 dÙãÜ×“ÏâÍ~æc+j·Jzâ7(£ðW]•æ™?nê´º6åwéåç÷N•ZŠíž›¬|?Ðõ?Ñ-E…Â®³ÇV$~X¯/…õ x‘LˆÑÜÚÈ7¦pzãÜüë½ðÄ^õtÝYËÍ7ÉÖÕ8ÏUe# #€r=sU¾/é’E§jRC4mxNÝ´9†íuá»›V‘ ZI€×cr1Ÿpzsøf»¨åV‹ìû`qËLÊIã?\~¼³áËC©êhªOîO»‘ÃmçÛçút×¢x“Z}?Ãœê#b-¤X7õÄò gž zzbº3œm*qvs·M=íúéw}¿&Úª°^Ö×µÏ(ø‡â†Öµƒenñý†×åQáYûœ÷ÇLœôÎNk¡ðÂ‡¼/µ¸n0æÉ0¬ƒ‚üîÉÆvŒw®Sáö”š¯‹-üÕVŠØÙ[$`(9cqƒÔ_@BëqûÙ`Ýæ0;79È?w<ó |ÙÜkßÌ1±Ëã¿ìÒ»ðlìï«ÓnªèèrP´NÏÂš&ŽéöÙ¸÷æ°~-_O'‰`°!RÚÚÝ%]Ø%þbß1'¿ÿ XÕáOöÎŒ·‹¬+Åæ*ÛÛ™0¤ƒOÍÔ`u¯¦ÂaèÐÃÓ«‹¨Ô¥µœ¿¯ÉyÅÙ.oÔôŸ Úx&(STðÝ½¦õ] ’ÒNóÁäÈùr3í·žÚ[™ƒ¼veÈÃ·ÞIõÎGlqÎ=M|«gsªxÅI6 ]Z·Îªä,¨zŒŽÄ~#ØŠúFñî™ªiÉqc©éÐD>Së”‘ GñŽ1éÐ^+ Ëi;Ô„µVÕú»i¯ÈÒ-ZÍ]òÜ˜®ì`bÛÙ¥_/y(@÷qÐúg Ô÷W0.Ø› 6Ò© r>QƒŒ0+Èîzb¨É+I0TbNñ"$~)ÕÒ6Þ‹{0VÆ27œWWñcÄcX×íôûyKZéðªc'iQ¿¯LaWŠŸS\·Š“ÅºÊ¸…ôÙÂí|öÀÇåV|!¤ÂGâÛ[[’ï 3OrÙËPY¹=Î1õ5öåTžÑè Ú64/üö?Zëžk}¬¶éàoá¾á}3“ü]8Éæ¿´n²Žš_6¾pœ)2?úWÓÚ¥¾¨iWúdŽq{*ª1rXŒd…m»‰äcô¯–dâ•ã‘Jº¬§¨#¨®§,df«8ÉÅßN¾hˆ;îÓ=7áùpën®É 6ûJžO2^œÐò JÖø¥²ãÂ›Ò6Ü·‰!wbÍ‚¬O©»õ¬ÿ ƒP=Ä:â¤-&ÙŽ `È9 r9íÏ§zë> XÅ7ƒ5X–krÑ¢L7€ìw}ÑŸNHëŒüþ:2†á¼+u·á÷N/Û'Ðç~ß˜ô«ëh!ónRéeQ´6QÛÿ èEwëÅÒ|¸Yqó1uêyùzð8 ƒŠù¦Ò;¹ä6öi<'ü³„[ÃZhu½ ùÍ¡g‚>r¯×ŠîÌx}bñ2“kê£§oø~›hTèóËWò4|ki"xßQ˜Ï6øÀLnß‚0 ¹Æ{±–¶Öe#¨27È@^Ìß.1N¾œyç€õ†ñeé·Õã†çQ°€=Ì©ºB€Ø8<‚ÃSõ®ùcc>×Ú .Fr:žÝGæ=kÁâ,^!Fž ¬,àµ}%¶«îõ¹†"r²ƒGœüYÕd?aÑÃY®49PyU ÷þ!žxÅm|/‚ãNð˜¼PcûTÒ,¹/Ý=FkÏ|u¨¶«âë…{¤m¢]Û¾ïP>®XãÞ½iÓÁ¾ ‰'¬–6ß¼(„ï— í!úÙäzôë^–:œ¨å|,_¿&š×]uÓÑµÛô4’j”bž§x‘Æ©ã›á,‚[Ã” ÎÞ= î®ˆŒËæ ÀùYÁ?ŽïÚ¼?ÁªxºÕÛ,°1¸‘¿ÝäãØ¯v…@¤åq½ºã œàûââ·z8Xýˆþz~—û»™âµj=Ž â~ãáh@'h¼F#·Üp?ŸëQü-løvépx»cŸø…lxâÃûGÂ·‰¶ø”L£©%y?¦úõÆü-Õ¶¥y`Òl7>q’2üA?•F}c‡jB:¸Jÿ +§¹¿¸Q÷°ív=VÑìu[Qml%R7a×IèTõéŽx¬ ?†š7 1†îã-ˆã’L¡lŽ0OÓ=ÅuˆpÇ•¼3ÛùÒ¶W/!|’wŽw^qÔ×ÏaóM8Q¨ãÑ?ëï0IEhÄa¸X•`a ?!ÐñùQ!Rä ÂžqŽžÝO`I0ÿ J“y|ñ!Îã@99>þ8–+éáu…!ù—ä Ê°<÷6’I®z ÅS„¾)Zþ_Öýµ×ËPåOwø÷þ*üïænÖùmØÝûþ¹=>¦½öî×Jh]¼ç&@§nTŒ6ITÀõ^Fxð7Å3!Ö·aÛ$þÿ ¹ã5îIo:ÈªmËY[’8ÇÓ¾Ç‰*òû¢¥xõ¾¼ú•åk+\ð¯ HÚoŽl•Ûk,¯ ç²²cõÅ{²Z\ ´ìQ åpzŽ3Ôð}ÿ Jð¯XO¡øÎé€hÙ¥ûLdŒ`““ù6Gá^ÃáÝ^Ë[Ñb¾YåŒÊ»dŽ4†2§,;ÿ CQÄ´¾°¨c–±”mºV{«ßÕýÄW\ÖŸ‘çŸ,çMRÆí“l-ƒn~ë©ÉÈê Ü?#Ž•¹ðãSÒ¥ÐWNíà½;ãž)™ÎSÈ9cóLjëµ¿Å«iÍk¨ió¶X‚7÷ƒ€yãnyÏŽëÞ Öt`×À×V's$È9Ú:ä{wÆEk€«†Çàc—â$éÎ.éí~Ýëk}ÅAÆpörÑ¢‡Šl¡ÑüSs‹¨‰IÃ„óÀ×wñ&eºðf™pŒÆ9gŽTø£lñëÀçŽ NkÊUK0U’p ï^¡ãÈ¥´ø{£ÙHp`’ØåbqÏ©äó^Æ: Ž' ÊóM«õz+ß×ó5Ÿ»('¹ð¦C„$˜Å¢_ºÈI?»^äã'ñêzž+ë€ñ-½»´}¡Ë*õ?.xÇ^1ŽMyÇÂ¸&“Â—L–îëöâ7…' bqéÎGé]Ëªâ1$o²¸R8Ã`.q€}sÖ¾C98cêÆÞíïóòvÓòùœÕfÔÚéýuèÖ·Ú Å‚_¤³ÜÛºÆ‘ÃŸ”à×¨ý:×ƒxPþÅÕî-/üØmnQìïGÎŠÙRqê=>¢½õnæ·r!—h`+’;ò3È<“Û©éšóŸx*÷V¹¸×tÈiˆßwiÔÿ |cŒñÏ®3Ö½Ì°‰Ë Qr©ö½®¼ÛoÑÙZÅÑ«Oàµ¯ýw8;k›ÿ x†;ˆJa;‘º9÷÷R+¡ñgŽí|Iáë{ôáo2Ê²9 029ÉÏLí\‰¿¸Ÿb˜ "Bv$£&#ßiê>=ªª©f ’N ëí>¡NXW~5×úíø\‰»½Ï^ø(—wÖú¥¤2íŽÞXæÁ$°eÈ888^nÝë²ñÝÔ^ ÖÚ9Q~Ëå7ï DC¶ÑµƒsËÇè9®Wáþƒ6‡£´·°2\Ý:ÈÑ?(#¨'$õèGJ¥ñW\ÿ ‰E¶—¸™g˜ÌÀ¹;Pv ú±ÎNs·ëŸ’–"Ž/:té+ûË]öJöÓM»ëø˜*‘•^Uý—êd|‰åñMæÔÝ‹23å™6æHùÛ‚ëüñ^…ñ1¢oêûÑEØ.õ7*ÅHtÎp{g<·Á«+¸c¿¿pÓ¾Æby=8É_ÄsÆk¬ñB\jÞÔì••Ë[9Píb‹Bãƒ… =93§ð§LšÛáÖšÆæXÌÞdÛP.0\ãïÛ0?™úJ¸™Ë ”•œº+=<µI£¦í¯õêt¬d‹T¬P=ËFêT>ÍØØ@Ï9<÷AQÌ×»Õ¡xùk",JÎæù±Éç$œŽŸZWH®¯"·UÌQÂ ’ÙÈ]ÅXg<ã ß¨g3-Üqe€0¢¨*Œ$Üƒ ’Sû 8ãŽ¼_/e'+Ï–-èÓ¶¶Õíß[·ÙÙ½îì—¼sk%§µxä‰â-pÒeÆCrú ôÏƒžû=”šÅô(QW‚Õd\ƒæ. \àö¹¯F½°³½0M>‘gr÷q+œ¶NïºHO— ¤ Ü¥Ý”n·J|ÆP6Kµc=Isó}Ò çGš)a=—#vK›åoK§ßóÙ¤¶¿õú…ÄRÚ[ËsöÙ¼Ë•Ë ópw®qœŒ·Ø ùÇâ‹ý‡ãKèS&ÞvûDAù‘É9ŒîqÅ} $SnIV[]Ñ´Ó}ØÜ¾A Ü|½kÅþÓ|EMuR¼.I¼¶däò‚ÃkÆ}ðy¹vciUœZ…Õõ»z¾÷¿n¦*j-É/àœHã\y5 Û ß™ó0—äŸnzôã#Ô¯,†¥ÚeÔ÷ÜÅ´„“'c…<íÝ€<·SŠ¥k§Ã¢éÆÆÙna‚8–=«Êª[Ÿ™°pNî02z“ÔÙ–K8.È’Þî(vƒ2®@ äÈûãçžxäÇf¯ˆu¹yUÕîýWšÙ|›ëÒ%Q^í[æ|éo5ï‚¼ZY•^{96ˆY‚§v*x>âº_|U¹Ö´©tûMÒÂ9PÇ#«£#€ éÉñ‘ƒÍz/‰´-Ä¯¹°dd,Ð‘›p03ƒœ{ç9=+ Ûá§‡¬¦[‡‚êå©º¸#±ß=³ý¿•Õµjñ½HÙh›Û[§ÚýÊöô÷{˜?ô÷·Ô.u©–_%còcAÀ˜’ }0x9Î>žñÇáÍ9,ahï¦Ì2òÓ ñÛAäry$V²Nð ]=$Ž ‚#Ù‚1ƒƒødõMax‡ÂÖ^!±KkÛ‘ «“Çó²FN8+ëÎ{Ò¼oí§[«ÕMRoËeç×[_m/¦¦k.kôgŽxsSÓ´ý`êzªÜÜKo‰cPC9ÎY‰#§^üý9¹âïÞx£Ë·Ú`±‰‹¤;³–=ÏaôÕAð‚÷kêÁNBéÎælcõö®£Fð†ô2Ò¬]ßÂK$ÓÜ®•”/ÊHàã$ä¸÷ëf¹Oµúâ“”’²øè´µþöjçNü÷üÌ¿ xNïFÒd»¼·h®îT9ŽAµÖ>qÁçÔœtïÒ»\È¶ÎîcÞäîó3¶@#ÉIÎ ÔñW.<´’¥–ÑÑ€ÕšA‚ ;†qÓë‚2q ÒÂó$# Çí‡ !Ë}Õ9ÈÎÑÉã=;ŒÇÎuñ+ÉûÏ¥öíeÙ+$úíÜå¨¯'+êZH4ƒq¶FV‹gïŒ208ÆÌ)íÐ±>M|÷âÍãÂ¾"iì‹¥£Jd´™OÝç;sÈúr+ÜäˆË)DŒ¥šF°*3Õ”d{zÔwºQ¿·UžÉf†~>I+ŒqÔ`ð3œ“Ü×f]œTÁÔn4“ƒø’Ýßõ_«*5šzGCÊ,þ+ê1Ã²÷O¶¸cœºb2yÇ;cùÕ£ñh¬›áÑŠr¤ÝäNBk¥—á—†gxšX/ì‘˜hŸ*Tçn =ûã¦2|(ð¿e·ºÖ$ ýìŸ!'åÎ°yîî+×öœ=Y:²¦ÓÞ×iü’—ü -BK™£˜›âÆ¡&véðõ-ûÉY¹=Onj¹ø¯¯yf4·±T Pó`çœ7={×mÃ/¢˜ZÚòK…G½¥b„’G AãÜœ*í¯Ã¿ IoæI¦NU8‘RwÈã;·€ Û×ëÒ”1Y •£E»ÿ Oyto¢<£Áö·šï,ä‰§ûA¼sû»Nò}¹üE{ÜÖªò1’õÞr0â}ÎØ#>à/8ïéÎ~—áÍ#Ã±Îlí§³2f'h”?C÷YËdð:qëõÓ·‚ïeÄ© ÔÈØÜRL+žAÎ3¼g=åšó³Œt3 ÑQ¦ùRÙßE®¼±w_;þhš’Sirÿ ^ˆã¼ià©‡|RòO„m°J/“$·l“ ÇÓ¿ÿ [ÑŠÆ“„†Õø>cFÆ6Ø1ƒ– àz7Ldòxäüwá‹ÝAXùO•Úý’é®ähm •NÀ±ÌTÈç ƒ‘I$pGž:‚ÄbêW¢®œ´|¦nÍ>¶ÖÏ¢§ÎÜ¢ºö¹•%ÄqL^öÛKpNA<ã¡ …î==ª¸óffËF‡yÌcÉ ©ç$ð=ñÏYþÊ’Ú]—¥‚¬‚eDïÎH>Ÿ_ÌTP™aÂ‰ch['çÆÜò7a‡?w°Ïn§âÎ5”’¨¹uÚÛ|´ÓÓc§{O—ü1•ªxsÃZ…ÊÏy¡Ã3¸Ë2Èé» ‘ƒÎ äžÜðA§cáOéúÛ4ý5-fŒï„ù¬ûô.Ç Üsž•Ò¾•wo<¶Ÿ"¬¡º|£ î2sÇ¡éE²ÉFÑ±rU°dÜ6œ¨ mc†Îxë×ºÞ'0²¡Rr„{j¾í·è›µ÷)º·å–‹î2|I®Y¼ºÍË·–ÃÆàã£'óÆxƒOÆÞ&>\lóÌxP Xc¸ì Sþ5§qà/ê>#žÞW¸if$\3 ® ûÄ“ùŽÕê¾ð<Ó‹H¶óÏ" å·( á‘€:ã†8Ï=+ê¨¬UA×ÃËÚT’ÑÞöù¥¢]{»ms¥F0\ÑÕ—ô}&ÛB´ƒOŽÚ+›xíÄÀ1 ,v± žIëíZ0Ç§™3í2®0à¸—p9öÝÔž)ÓZËoq/Ú“‘L ²ŒmùŽï‘Ó9§[Û#Ä‘\ÞB¬Çs [;à à«g‚2ôòªœÝV§»·¯/[uó½õÛï¾ /šÍ}öüÿ «=x»HŸÂÞ.™ ÌQùŸh´‘#a$‚'¡u<Š›Æ>2>+ƒLSiöwµFó1!eg`£åœ ÷ëÛö}Á¿ÛVÙêv $¬ƒ|,s÷z€ðÎƒ¨x÷ÅD\ÜŒÞmåÔ„ ˆ o| :{ÇÓ¶–òÁn!´0Ål€, ƒ ( ÛŒŒc¶rsšæ,4‹MÛOH!@¢ ÇŽ„`å²9ÝÃw;AÍt0®¤¡…¯ØÄ.Àìí´ƒ‘ßñ5Í,Óëu-ÈÔc¢KÃÓ£òÖÌºU.õL¯0…%2È—"~x ‚[`có±nHàŽyàö™¥keˆìŒÛFç{(Ø©†`Jã#Žwg<“:ÚÉ;M ^\yhûX‡vB·÷zrF?§BÊÔ/s<ÐÈB)Û± ·ÍÔwç5Âã:så§e{mÑ¤ï«Òíh—]Wm4âí¿ùþW4bC3¶ª¾Ùr$pw`àädzt!yŠI„hÂîàM)!edŒm'æ>Ç?wzºKìcŒ´¯Ìq6fp$)ãw¡éUl`µ»ARAˆÝÕgr:äŒgƒéé[Ôö±”iYs5Ýï«ÙG—K=þF’æMG«óÿ `ŠKÉ¦uOQ!ÕåŒ/ÎGÞ`@ËqÕzdõâ«Ê/Ö(ƒK´%ŽbMüåÜŸö—>¤óŒŒV‘°„I¢Yž#™¥ùÏÊ@8 œgqöö5ª4v×“[¬(q cò¨À!FGaÁõõ¯?§†¥ÏU½í¿WªZ$úyú½Žz×§Éþ?>Ã×È•6°{™™ŽÙ.$`ÎUœ…çè ' ¤r$1Ø(y7 ðV<ž:È ÁÎMw¾Â'Øb§øxb7gãÐž½óÉÊë²,i„FÈ¹£§8ãäÂ½k¹¥¦ê/ç{ïêï¦‡2œ/«ü?¯Ô›ìñÜ$þeýœRIåŒg9Ác’zrrNO bÚi¢ ÑºË/$,“ª¯Ýä;Œ× ´<ÛÑn³IvŸb™¥ nm–ÄŸ—nÝÀãŽ3ëÍG,.öó³˜Ù£¹uÊÌrŠ[<±!@Æ:c9ÅZh ì’M5ÄìÌ-‚¼ëÉùqŽGì9¬á ;¨A-ž—évþÖ–^ON·Ô”ŸEý}ú×PO&e[]ÒG¸˜Ûp ƒÃà/Ë·8ûÀ€1ž@¿ÚB*²¼ñì8@p™8Q“žÆH'8«I-%¸‚ F»“åó6°Uù|¶Ú¸ã ò^Äw¥ŠÖK–1ÜÝK,Žddlí²0PÀü“×ükG…¯U«·¶–´w¶ŽÍ¾©yÞú[Zös•¯Á[™6° ¨¼ÉVæq·,# ìãï‘×8îry®A››¨,ãc66»Ë´ã'æÉù?t}¢æH--Òá"›|ˆ¬[í 7¶ö#¸9«––‹$,+Ëqœ\Êøc€yê^Ý¸Äa°«™B-9%«×®‹V´w~vÜTéê¢·þ¼ˆ%·¹• ’[xç•÷2gØS?6åÀÚ õ9É#š@÷bT¸º²C*3Bá¤òÎA9 =úU§Ó"2Ãlá0iÝIc‚2Î@%öç94ùô»'»HÄ¥Ô¾@à Tp£šíx:úÊ:5eºßMý×wµ›Ó_+šº3Ýyvÿ "ºÇ<ÂI>Õ1G·Ë«È«É# àÈÇ øp Jv·šæDûE¿›†Ë’NFr2qŸ½ÇAÜšu•´éí#Ä¦8£2”Ú2Ã/€[ÎTr;qŠz*ý’Îþ(â‰ ;¡TÆâ›;ºÿ àçœk‘Þ8¾Uª¾íé{^×IZéwÓkXÉûÑZo¯_øo×È¡¬ â–ÞR§2„‚Àœü½ùç® SVa†Âüª¼±D‘ŒísŸàä|ä2 æ[‹z”¯s{wn„ÆmáóCO+†GO8Ïeçåº`¯^¼ðG5f{Xžä,k‰<á y™¥voÆ éÛõëI=œ1‹éíÔÀÑ)R#;AÂncäŽ:tÏ#¶TkB.0Œ-ÖÞZÛgumß}fÎJÉ+#2êÔP£žùÈÅi¢%œ3P*Yƒò‚Aì“Ž2r:ƒÐúñiRUQq‰H9!”={~¼“JŽV¥»×²m.ÛßºiYl¾òk˜gL³·rT• ’…wHÁ6ä`–Î3ùÌ4Øe³†&òL‘•%clyÃ®AÂäà0 žüç$[3uÅ˜î¹•pNOÀÉ=† cï{rYK ååä~FÁ •a»"Lär1Ó¯2Äõæ<™C•.fÕ»è¥~½-¿g½Â4¡{[ør¨¶·Žõäx¥’l®qpwÇ»8ärF \cŽ¸ÜÆÓ-g‚yciÏÀ¾rÎwèØÈ#o°Á9ã5¢šfÔxÞæfGusÏÌJÿ µ×œ/LtãÅT7²¶w,l É³;”eúà·¨çîŒsÜgTÃS¦^ '~‹®›¯+k÷ZÖd©Æ*Ó[Ü«%Œk0ŽXƒ”$k#È¨ P2bv‘ƒŸáÇ™ÆÕb)m$É*8óLE‘8'–ÜN Úyàúô+{uº±I'wvš4fÜr íì½=úuú sFlìV$‘ö†HÑù€$§ õ=½¸«Ž] :Ž+•¦ïmRþ½l´îÊT#nkiøÿ _ðÆT¶7Ò½ºÒ£Î¸d\ã8=yãŽÜäR{x]ZâÚé#¸r²#»ÎHÆ6õ ç® ÎFkr;sºÄ.&;só±Ç9êH÷ýSšÕtÐU¢-n Ì| vqœ„{gŒt§S.P‹’Ž‰_[;m¥ÞZýRûÂX{+¥úü¼ú•-àÓ7!„G"“´‹žƒnrYXã¸îp éœ!ÓoPÌtÑ (‰Þ¹é€sÓ#GLçÕšÑnJý¡!‘Tä#“ß?îýp}xÇ‚I¥Õn#·¸–y'qó@r[ Êô÷<ÔWÃÓ¢áN¥4Ô’I&Ý¼¬¬¼ÞºvéÆ FQV~_ÒüJÖÚt¥¦Xá3BÄP^%ÈÎW-×c¡ú©¤·Iþèk¥š?–UQåIR[’O 5x\ÉhÆI¶K4«2ùªŠŒ<¼óœçØ`u«‚Í.VHä€ Ëgfx''9ÆI#±®Z8 sISºku¢ßÞ]úk»Jößl¡B.Ü»ÿ MWe °·Ž%šêÉ†¼»Âù³´œ O¿cÐÓÄh©"ÛÜÏ.ÖV’3nüÄmnq[ŒòznšÖ>J¬òˆæ…qýØP Ž:ä7^0yëWšÍ_79äoaÈ °#q0{ää×mœy”R{vÒÞ¶ÚÏe¥“ÚÆÐ¥Ì®—õýjR •íç›Ìb„+JyÜØÙ•Ç]¿Ôd þËOL²”9-Œ—õÃc'æÝ×œçÚ²ìejP“½ âù°¨†ðqòädÐƒÉäÖÜj÷PÇp“ÍšŠå«‘î <iWNsmª»¶vÓz5»ûì:Rs\Ðßôû×uÔÿÙ