Vladimir Keleshev

> For a flag to have an argument, you need to explicitly say so in an `Options:` section. This is required only in ambiguous cases like `--input `, but not...

I think introduction of arguments' defaults is the right way to solve this.

I think headers make it less flexible (you might want several headers for both options and arguments). I think usage-pattern should be taken out of parsing option/arguments description/defaults.

I think being dependent on indentation is very subtle in this case. Why not: - If line starts with {word starting with ``, or an upper case word}, which follows...

@Met48, I can see that you are a very active contributor to docopt—that is very appreciated. You know, it can be frustrating if your hard work is not pulled into...

Support upcoming, see #37

no, not yet

I'm afraid not. Not until #104 is implemented. But that is because it's so easy to get around. You can still put `[default: foo]` in your documentation, but in code...

That sounds great. On license: that sounds ok, but could you write up on "why". Isn't MIT general enough to be included together with almost any other software? Take a...

Looks good, do you want to move it to docopt organization?