summaryrefslogtreecommitdiff
path: root/examples/python_scripting.py
diff options
context:
space:
mode:
authorKevin Van Brunt <kmvanbrunt@gmail.com>2019-06-15 00:53:23 -0400
committerKevin Van Brunt <kmvanbrunt@gmail.com>2019-06-15 00:53:23 -0400
commitbeb2b37e5488965f7b2e240ea7453234bcbd3cd1 (patch)
tree9ec803a7036d5f3d680610ab5daba78e5c38a37d /examples/python_scripting.py
parentdf8679b3331a8aebd3af4bbe2a0c6e625346f348 (diff)
downloadcmd2-git-beb2b37e5488965f7b2e240ea7453234bcbd3cd1.tar.gz
Updated documentation
Diffstat (limited to 'examples/python_scripting.py')
-rwxr-xr-xexamples/python_scripting.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/examples/python_scripting.py b/examples/python_scripting.py
index da7d0f6a..88bc2f98 100755
--- a/examples/python_scripting.py
+++ b/examples/python_scripting.py
@@ -9,8 +9,8 @@ learn to create scripts.
However, there comes a time when technical end users want more capability and power. In particular it is common that
users will want to create a script with conditional control flow - where the next command run will depend on the results
-from the previous command. This is where the ability to run Python scripts inside a cmd2 application via the pyscript
-command and the "pyscript <script> [arguments]" syntax comes into play.
+from the previous command. This is where the ability to run Python scripts inside a cmd2 application via the
+run_pyscript command and the "run_pyscript <script> [arguments]" syntax comes into play.
This application and the "scripts/conditional.py" script serve as an example for one way in which this can be done.
"""