Package: docopt-mpe
docoptcreatesbeautifulcommand-line interfacesThis is a 0.6.x fork of docopt, adding access to docopt internal
objects usingdocopt(...return_spec=true).Also adding anOption.metaattribute, to try to remember the original name
of the value placeholder.Argument.nameis already available.This is like the ‘meta’ attribute onoptparse.Option’s.
Supported by docopt:<Meta-or-Arg-Name>
META-OR-ARG-NAMEThis should enable a way to leverage some rudimentary validation or
input parsing of the values, by associating handlers to meta names.Video introduction todocopt:PyCon UK 2012: Create *beautiful*
command-line interfaces with PythonNew in version 0.6.1:Fix issue#85which caused improper handling of[options]shortcut
if it was present several times.New in version 0.6.0:New argumentoptions_first, disallows interspersing options
and arguments.  If you supplyoptions_first=Truetodocopt, it will interpret all arguments as positional
arguments after first positional argument.If option with argument could be repeated, its default value
will be interpreted as space-separated list. E.g. with[default: ./here ./there]will be interpreted as['./here','./there'].Breaking changes:Meaning of[options]shortcut slightly changed. Previously
it ment“any known option”. Now it means“any option not in
usage-pattern”.  This avoids the situation when an option is
allowed to be repeated unintentionaly.argvisNoneby default, notsys.argv[1:].
This allowsdocoptto always use thelatestsys.argv,
notsys.argvduring import time.Isn’t it awesome howoptparseandargparsegenerate help
messages based on your code?!Hell no!You know what’s awesome?  It’s when the option parserisgenerated based on the beautiful help message that you write yourself!
This way you don’t need to write this stupid repeatable parser-code,
and instead can write only the help message–the way you want it.docopthelps you create most beautiful command-line interfaceseasily:"""Naval Fate.

Usage:
  naval_fate.py ship new <name>...
  naval_fate.py ship <name> move <x> <y> [--speed=<kn>]
  naval_fate.py ship shoot <x> <y>
  naval_fate.py mine (set|remove) <x> <y> [--moored | --drifting]
  naval_fate.py (-h | --help)
  naval_fate.py --version

Options:
  -h --help     Show this screen.
  --version     Show version.
  --speed=<kn>  Speed in knots [default: 10].
  --moored      Moored (anchored) mine.
  --drifting    Drifting mine.

"""fromdocoptimportdocoptif__name__=='__main__':arguments=docopt(__doc__,version='Naval Fate 2.0')print(arguments)Beat that! The option parser is generated based on the docstring above
that is passed todocoptfunction.docoptparses the usage
pattern ("Usage:...") and option descriptions (lines starting
with dash “-”) and ensures that the program invocation matches the
usage pattern; it parses options, arguments and commands based on
that. The basic idea is thata good help message has all necessary
information in it to make a parser.Also,PEP 257recommends
putting help message in the module docstrings.InstallationUsepipor easy_install:pip install docopt==0.6.2Alternatively, you can just dropdocopt.pyfile into your
project–it is self-contained.docoptis tested with Python 2.5, 2.6, 2.7, 3.2, 3.3 and PyPy.APIfromdocoptimportdocoptdocopt(doc,argv=None,help=True,version=None,options_first=False)docopttakes 1 required and 4 optional arguments:doccould be a module docstring (__doc__) or some other
string that contains ahelp messagethat will be parsed to
create the option parser.  The simple rules of how to write such a
help message are given in next sections.  Here is a quick example of
such a string:"""Usage: my_program.py [-hso FILE] [--quiet | --verbose] [INPUT ...]

-h --help    show this
-s --sorted  sorted output
-o FILE      specify output file [default: ./test.txt]
--quiet      print less text
--verbose    print more text

"""argvis an optional argument vector; by defaultdocoptuses
the argument vector passed to your program (sys.argv[1:]).
Alternatively you can supply a list of strings like['--verbose','-o','hai.txt'].help, by defaultTrue, specifies whether the parser should
automatically print the help message (supplied asdoc) and
terminate, in case-hor--helpoption is encountered
(options should exist in usage pattern, more on that below). If you
want to handle-hor--helpoptions manually (as other
options), sethelp=False.version, by defaultNone, is an optional argument that
specifies the version of your program. If supplied, then, (assuming--versionoption is mentioned in usage pattern) when parser
encounters the--versionoption, it will print the supplied
version and terminate.versioncould be any printable object,
but most likely a string, e.g."2.1.0rc1".Note, whendocoptis set to automatically handle-h,--helpand--versionoptions, you still need to mention
them in usage pattern for this to work. Also, for your users to
know about them.options_first, by defaultFalse.  If set toTruewill
disallow mixing options and positional argument.  I.e. after first
positional argument, all arguments will be interpreted as positional
even if the look like options.  This can be used for strict
compatibility with POSIX, or if you want to dispatch your arguments
to other programs.Thereturnvalue is a simple dictionary with options, arguments
and commands as keys, spelled exactly like in your help message.  Long
versions of options are given priority. For example, if you invoke the
top example as:naval_fate.py ship Guardian move 100 150 --speed=15the return dictionary will be:{'--drifting':False,'mine':False,'--help':False,'move':True,'--moored':False,'new':False,'--speed':'15','remove':False,'--version':False,'set':False,'<name>':['Guardian'],'ship':True,'<x>':'100','shoot':False,'<y>':'150'}Help message formatHelp message consists of 2 parts:Usage pattern, e.g.:Usage: my_program.py [-hso FILE] [--quiet | --verbose] [INPUT ...]Option descriptions, e.g.:-h --help    show this
-s --sorted  sorted output
-o FILE      specify output file [default: ./test.txt]
--quiet      print less text
--verbose    print more textTheir format is described below; other text is ignored.Usage pattern formatUsage patternis a substring ofdocthat starts withusage:(caseinsensitive) and ends with avisiblyempty line.
Minimum example:"""Usage: my_program.py

"""The first word afterusage:is interpreted as your program’s name.
You can specify your program’s name several times to signify several
exclusive patterns:"""Usage: my_program.py FILE
          my_program.py COUNT FILE

"""Each pattern can consist of the following elements:<arguments>,ARGUMENTS. Arguments are specified as either
upper-case words, e.g.my_program.pyCONTENT-PATHor words
surrounded by angular brackets:my_program.py<content-path>.–options.  Options are words started with dash (-), e.g.--output,-o.  You can “stack” several of one-letter
options, e.g.-oivwhich will be the same as-o-i-v. The
options can have arguments, e.g.--input=FILEor-iFILEor
even-iFILE. However it is important that you specify option
descriptions if you want for option to have an argument, a default
value, or specify synonymous short/long versions of option (see next
section on option descriptions).commandsare words that donotfollow the described above
conventions of--optionsor<arguments>orARGUMENTS,
plus two special commands: dash “-” and double dash “--”
(see below).Use the following constructs to specify patterns:[ ](brackets)optionalelements.  e.g.:my_program.py[-hvqoFILE]( )(parens)requiredelements.  All elements that arenotput in[ ]are also required, e.g.:my_program.py--path=<path><file>...is the same asmy_program.py(--path=<path><file>...).  (Note, “required options” might be not
a good idea for your users).|(pipe)mutualy exclusiveelements. Group them using(
)if one of the mutually exclusive elements is required:my_program.py(--clockwise|--counter-clockwise)TIME. Group
them using[ ]if none of the mutually-exclusive elements are
required:my_program.py[--left|--right].…(ellipsis)one or moreelements. To specify that
arbitrary number of repeating elements could be accepted, use
ellipsis (...), e.g.my_program.py FILE ...means one or
moreFILE-s are accepted.  If you want to accept zero or more
elements, use brackets, e.g.:my_program.py [FILE...]. Ellipsis
works as a unary operator on the expression to the left.[options](case sensitive) shortcut for any options.  You can
use it if you want to specify that the usage pattern could be
provided with any options defined below in the option-descriptions
and do not want to enumerate them all in usage-pattern.  -
“[--]”. Double dash “--” is used by convention to separate
positional arguments that can be mistaken for options. In order to
support this convention add “[--]” to you usage patterns.  -
“[-]”. Single dash “-” is used by convention to signify thatstdinis used instead of a file. To support this add “[-]”
to you usage patterns. “-” act as a normal command.If your pattern allows to match argument-less option (a flag) several
times:Usage: my_program.py [-v | -vv | -vvv]then number of occurences of the option will be counted. I.e.args['-v']will be2if program was invoked asmy_program-vv. Same works for commands.If your usage patterns allows to match same-named option with argument
or positional argument several times, the matched arguments will be
collected into a list:Usage: my_program.py <file> <file> --path=<path>...I.e. invoked withmy_program.py file1 file2--path=./here--path=./therethe returned dict will containargs['<file>']== ['file1', 'file2']andargs['--path']==['./here','./there'].Option descriptions formatOption descriptionsconsist of a list of options that you put
below your usage patterns.It is necessary to list option descriptions in order to specify:synonymous short and long options,if an option has an argument,if option’s argument has a default value.The rules are as follows:Every line indocthat starts with-or--(not counting
spaces) is treated as an option description, e.g.:Options:
  --verbose   # GOOD
  -o FILE     # GOOD
Other: --bad  # BAD, line does not start with dash "-"To specify that option has an argument, put a word describing that
argument after space (or equals “=” sign) as shown below. Follow
either <angular-brackets> or UPPER-CASE convention for options’
arguments.  You can use comma if you want to separate options. In
the example below, both lines are valid, however you are recommended
to stick to a single style.:-o FILE --output=FILE       # without comma, with "=" sign
-i <file>, --input <file>   # with comma, wihtout "=" singUse two spaces to separate options with their informal description:--verbose More text.   # BAD, will be treated as if verbose option had
                       # an argument "More", so use 2 spaces instead
-q        Quit.        # GOOD
-o FILE   Output file. # GOOD
--stdout  Use stdout.  # GOOD, 2 spacesIf you want to set a default value for an option with an argument,
put it into the option-description, in form[default:<my-default-value>]:--coefficient=K  The K coefficient [default: 2.95]
--output=FILE    Output file [default: test.txt]
--directory=DIR  Some directory [default: ./]If the option is not repeatable, the value inside[default:...]will be interpeted as string.  If itisrepeatable, it will be
splited into a list on whitespace:Usage: my_program.py [--repeatable=<arg> --repeatable=<arg>]
                     [--another-repeatable=<arg>]...
                     [--not-repeatable=<arg>]

# will be ['./here', './there']
--repeatable=<arg>          [default: ./here ./there]

# will be ['./here']
--another-repeatable=<arg>  [default: ./here]

# will be './here ./there', because it is not repeatable
--not-repeatable=<arg>      [default: ./here ./there]ExamplesWe have an extensive list ofexampleswhich cover
every aspect of functionality ofdocopt.  Try them out, read the
source if in doubt.Subparsers, multi-level help andhugeapplications (like git)If you want to split your usage-pattern into several, implement
multi-level help (whith separate help-screen for each subcommand),
want to interface with existing scripts that don’t usedocopt, or
you’re building the next “git”, you will need the newoptions_firstparameter (described in API section above). To get you started quickly
we implemented a subset of git command-line interface as an example:examples/gitData validationdocoptdoes one thing and does it well: it implements your
command-line interface.  However it does not validate the input data.
On the other hand there are libraries likepython schemawhich make validating data a
breeze.  Take a look atvalidation_example.pywhich usesschemato validate data and report an error to the
user.DevelopmentWe wouldloveto hear what you think aboutdocopton ourissues
pageMake pull requrests, report bugs, suggest ideas and discussdocopt. You can also drop a line directly to
<vladimir@keleshev.com>.Portingdocoptto other languagesWe thinkdocoptis so good, we want to share it beyond the Python
community!The follosing ports are available:Ruby portCoffeeScript portLua portPHP portBut you can always create a port for your favorite language!  You are
encouraged to use the Python version as a reference implementation.  A
Language-agnostic test suite is bundled withPython implementation.Porting discussion is onissues page.Changelogdocoptfollowssemantic versioning.  The
first release with stable API will be 1.0.0 (soon).  Until then, you
are encouraged to specify explicitly the version in your dependency
tools, e.g.:pip install docopt==0.6.20.6.2Wheelsupport.0.6.1 Bugfix release.0.6.0options_firstparameter.Breaking changes: Corrected[options]meaning.argvdefaults toNone.0.5.0 Repeated options/commands are counted or accumulated into a
list.0.4.2 Bugfix release.0.4.0 Option descriptions become optional,
support for “--” and “-” commands.0.3.0 Support for (sub)commands likegit remote add.
Introduce[options]shortcut for any options.Breaking changes:docoptreturns dictionary.0.2.0 Usage pattern matching. Positional arguments parsing based on
usage patterns.Breaking changes:docoptreturns namespace (for arguments),
not list. Usage pattern is formalized.0.1.0 Initial release. Options-parsing only (based on options
description).