summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDavid Lord <davidism@gmail.com>2020-02-16 17:31:04 -0800
committerDavid Lord <davidism@gmail.com>2020-02-16 17:31:04 -0800
commit7817ae6701767a73c608e00874115cb409591f8b (patch)
tree0aa46f3c67006f6ccfa48d9274968396d8c88750 /docs
parent79338495efca3ace77edce14e8f70587f1a11efa (diff)
downloadclick-7817ae6701767a73c608e00874115cb409591f8b.tar.gz
docs cleanup
Diffstat (limited to 'docs')
-rw-r--r--docs/why.rst25
1 files changed, 12 insertions, 13 deletions
diff --git a/docs/why.rst b/docs/why.rst
index 85e6a90..9418bfe 100644
--- a/docs/why.rst
+++ b/docs/why.rst
@@ -45,25 +45,24 @@ looking at the :ref:`complex-guide` chapter.
Why not Argparse?
-----------------
-Click is internally based on ``optparse`` instead of ``argparse``. This
+Click is internally based on ``optparse`` instead of ``argparse``. This
is an implementation detail that a user does not have to be concerned
-with. The reason Click is not using argparse is it has some
-problematic behaviors that make handling arbitrary command line interfaces
-hard:
-
-* argparse has built-in magic behavior to guess if something is an
- argument or an option. This behavior becomes a problem when dealing with
- incomplete command lines; the parsers behaviour becomes unpredictable
- without full knowledge of a command line. This goes against Click's
+with. Click is not based on argparse because it has some behaviors that
+make handling arbitrary command line interfaces hard:
+
+* argparse has built-in behavior to guess if something is an
+ argument or an option. This becomes a problem when dealing with
+ incomplete command lines; the behaviour becomes unpredictable
+ without full knowledge of a command line. This goes against Click's
ambitions of dispatching to subparsers.
-* argparse currently does not support disabling of interspersed
- arguments. Without this feature, it's not possible to safely implement
- Click's nested parsing nature.
+* argparse does not support disabling interspersed arguments. Without
+ this feature, it's not possible to safely implement Click's nested
+ parsing.
Why not Docopt etc.?
--------------------
-Docopt, and many tools like, it are cool in how they work, but very few of
+Docopt, and many tools like it, are cool in how they work, but very few of
these tools deal with nesting of commands and composability in a way like
Click. To the best of the developer's knowledge, Click is the first
Python library that aims to create a level of composability of applications