summaryrefslogtreecommitdiff
path: root/plac/doc/plac_core.txt
diff options
context:
space:
mode:
Diffstat (limited to 'plac/doc/plac_core.txt')
-rw-r--r--plac/doc/plac_core.txt9
1 files changed, 4 insertions, 5 deletions
diff --git a/plac/doc/plac_core.txt b/plac/doc/plac_core.txt
index 6012198..db90ec8 100644
--- a/plac/doc/plac_core.txt
+++ b/plac/doc/plac_core.txt
@@ -88,10 +88,7 @@ the boilerplate from nine lines to six lines:
.. include:: example2.py
:literal:
-However saving three lines does not justify introducing the external
-dependency: most people will not switch to Python 2.7, which at the time of
-this writing is just about to be released, for many years.
-Moreover, it just feels too complex to instantiate a class and to
+However, it just feels too complex to instantiate a class and to
define a parser by hand for such a trivial task.
The plac_ module is designed to manage well such use cases, and it is able
@@ -139,6 +136,8 @@ the usage message for free:
.. include:: example5.help
:literal:
+Notice that by default plac_ prints the string representation
+of the default values (with square brackets) in the usage message.
plac_ manages transparently even the case when you want to pass a
variable number of arguments. Here is an example, a script running
on a database a series of SQL scripts:
@@ -156,7 +155,7 @@ the command-line arguments parser to use from the signature of the main
function*. This is the whole idea behind plac_: if the intent is clear,
let's the machine take care of the details.
-plac_ is inspired to an old Python Cookbook recipe (optionparse_), in
+plac_ is inspired to an old Python Cookbook recipe of mine (optionparse_), in
the sense that it delivers the programmer from the burden of writing
the parser, but is less of a hack: instead of extracting the parser
from the docstring of the module, it extracts it from the signature of