diff options
| author | Armin Ronacher <armin.ronacher@active-4.com> | 2018-12-18 22:16:55 +0100 |
|---|---|---|
| committer | David Lord <davidism@gmail.com> | 2018-12-31 08:23:25 -0800 |
| commit | 031f4e85cea37bb7a58741fbfd3809bf7612ceeb (patch) | |
| tree | 3dc1cda10ca67e0e5ea4b22a28bc8293e0202639 /docs/why.rst | |
| parent | 43eb54db0bcde78dceaccfea9396ca21982003dd (diff) | |
| download | click-031f4e85cea37bb7a58741fbfd3809bf7612ceeb.tar.gz | |
Clarify optparse relationship
Diffstat (limited to 'docs/why.rst')
| -rw-r--r-- | docs/why.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/why.rst b/docs/why.rst index 76b84e7..65898f5 100644 --- a/docs/why.rst +++ b/docs/why.rst @@ -22,11 +22,11 @@ There are many alternatives to Click and you can have a look at them if you enjoy them better. The obvious ones are ``optparse`` and ``argparse`` from the standard library. -Click is actually implemented as a wrapper around a mild fork of -``optparse`` and does not implement any parsing itself. The reason it's -not based on ``argparse`` is that ``argparse`` does not allow proper -nesting of commands by design and has some deficiencies when it comes to -POSIX compliant argument handling. +Click is actually implements its own parsing of arugments and does not use +``optparse`` or ``argparse`` following the ``optparse`` parsing behavior. +The reason it's not based on ``argparse`` is that ``argparse`` does not +allow proper nesting of commands by design and has some deficiencies when +it comes to POSIX compliant argument handling. Click is designed to be fun to work with and at the same time not stand in your way. It's not overly flexible either. Currently, for instance, it |