docopt 0.6 fails to handle very simple usage message with two subcommands #85

schmir · 2013-02-01T15:12:47Z

There's a rather serious regression in docopt 0.6.

The following program fails to parse a simple "fs fail --loglevel
5". Instead it prints the usage message:

#! /usr/bin/env python

"""
Usage:
  fs good [options]
  fs fail [options]

Options:
      --loglevel=<level>       loglevel
"""

import docopt
print docopt.docopt(__doc__)

i.e. with docopt 0.6 I get

[dev]  ~/ % ./fs good --loglevel 5
{'--loglevel': '5',
 'fail': False,
 'good': True}
[dev]  ~/ % ./fs fail --loglevel 5
Usage:
  fs good [options]
  fs fail [options]

Without the --loglevel parameter it's working:

[dev]  ~/ % ./fs fail
{'--loglevel': None,
 'fail': True,
 'good': False}

with 0.5 I get the expected results:

[dev]  ~/ % ./fs good --loglevel 5
{'--loglevel': '5',
 'fail': False,
 'good': True}
[dev]  ~/ % ./fs fail --loglevel 5
{'--loglevel': '5',
 'fail': True,
 'good': False}

keleshev · 2013-02-01T20:24:43Z

This is now on PyPI: http://pypi.python.org/pypi/docopt

schmir mentioned this issue Feb 1, 2013

fix option parsing with multiple subcommands containing '[options]' #86

Merged

keleshev closed this as completed Feb 1, 2013

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docopt 0.6 fails to handle very simple usage message with two subcommands #85

docopt 0.6 fails to handle very simple usage message with two subcommands #85

docopt 0.6 fails to handle very simple usage message with two subcommands #85

docopt 0.6 fails to handle very simple usage message with two subcommands #85

Comments