CmampTask12067_Read_docs_about_DataPull_4 (#698)

* Update

Pre-commit checks:
- 'check_master' passed
- 'check_author' passed
- 'check_file_size' passed
- 'check_python_compile' passed
- 'check_gitleaks' passed
All checks passed ✅

* Improve

* Improve

* Lint

Author: gpsaggese

dev_scripts_helpers/coding_tools/parallel_script_skeleton.py renamed to dev_scripts_helpers/coding_tools/parallel_script_template.py

@@ -5,18 +5,18 @@
 parallel.
 
 # Run with:
-> clear; parallel_script_skeleton.py --workload success --num_threads serial
-> clear; parallel_script_skeleton.py --workload success --num_threads 2
-> clear; parallel_script_skeleton.py --workload failure --num_threads serial
-> clear; parallel_script_skeleton.py --workload failure --num_threads 3
+> clear; parallel_script_template.py --workload success --num_threads serial
+> clear; parallel_script_template.py --workload success --num_threads 2
+> clear; parallel_script_template.py --workload failure --num_threads serial
+> clear; parallel_script_template.py --workload failure --num_threads 3
 
 Add a description of what the script does and examples of command lines.
 Check dev_scripts/linter.py to see an example of a script using this
 template.
 
 Import as:
 
-import dev_scripts_helpers.parallel_script_skeleton as dspascsk
+import dev_scripts_helpers.parallel_script_template as dspascsk
 """
 
 # TODO(gp): We should test this, although the library is already tested.

dev_scripts_helpers/coding_tools/script_skeleton.py renamed to dev_scripts_helpers/coding_tools/script_template.py

@@ -8,7 +8,7 @@
 
 Import as:
 
-import dev_scripts_helpers.script_skeleton as dscscske
+import dev_scripts_helpers.script_template as dscscske
 """
 
 import argparse

dev_scripts_helpers/coding_tools/transform_skeleton.py renamed to dev_scripts_helpers/coding_tools/transform_template.py

@@ -1,20 +1,19 @@
 #!/usr/bin/env python
 
 """
-This is a skeleton example for a script that reads value from stdin or file,
+This is a template example for a script that reads value from stdin or file,
 transforms it, and writes it to stdout or file.
 
 This pattern is useful for integrating with editors (e.g., vim).
 
 Import as:
 
-import dev_scripts_helpers.transform_skeleton as dsctrske
+import dev_scripts_helpers.transform_template as dsctrske
 """
 
 import argparse
 import logging
 
-import helpers.hdbg as hdbg
 import helpers.hparser as hparser
 
 _LOG = logging.getLogger(__name__)

dev_scripts_helpers/documentation/run_pandoc.py

@@ -13,7 +13,7 @@
 :'<,'>!dev_scripts/documentation/run_pandoc.py -i - -o - -v CRITICAL
 ```
 
-This script is derived from `dev_scripts/transform_skeleton.py`.
+This script is derived from `dev_scripts/transform_template.py`.
 """
 
 import argparse

dev_scripts_helpers/old/fix_helpers_imports.sh

@@ -159,7 +159,7 @@ $replace_text --old 'import helpers.translate' --new 'import helpers.htranslate'
 (cd $AMP_DIR;git mv helpers/unit_test.py helpers/hunit_test.py)
 $replace_text --old 'import helpers.unit_test' --new 'import helpers.hunit_test'
 
-#unit_test_skeleton.py
+#unit_test_template.py
 
 #versioning.py
 (cd $AMP_DIR;git mv helpers/versioning.py helpers/hversion.py)

docs/code_guidelines/all.code_like_pragmatic_programmer.how_to_guide.md

@@ -472,7 +472,7 @@
   - E.g., write prototype in Python and then code the production system in C++
 
 - Tracer code:
-  - Build architectural skeleton
+  - Build architectural template
   - Components have minimal implementation
   - Over time stubbed routines are completed
   - The framework stays intact

docs/code_guidelines/all.coding_style.how_to_guide.md

@@ -73,7 +73,7 @@
     + [Examples of imports](#examples-of-imports)
   * [Scripts](#scripts)
     + [Use Python and not bash for scripting](#use-python-and-not-bash-for-scripting)
-    + [Skeleton for a script](#skeleton-for-a-script)
+    + [Template for a script](#template-for-a-script)
     + [Some useful patterns](#some-useful-patterns)
     + [Use scripts and not notebooks for long-running jobs](#use-scripts-and-not-notebooks-for-long-running-jobs)
     + [Follow the same structure](#follow-the-same-structure)
@@ -340,7 +340,7 @@
   - The name needs to be (possibly) short and memorable
     - However, don't be afraid to use long names, if needed, e.g.,
       `process_text_with_full_pipeline_twitter_v1`
-    - Сlarity is more important than number of bytes used
+    - Clarity is more important than number of bytes used
   - The name should capture what the object represents, without reference to
     things that can change or to details that are not important
   - The name should refer to what objects do (i.e., mechanisms), rather than how
@@ -1213,17 +1213,17 @@
 - Our approach is to make simple to create scripts in Python that are equivalent
   to sequencing shell commands, so that can evolve in complex scripts
 
-#### Skeleton for a script
+#### Template for a script
 
 - The ingredients are:
-  - [`/dev_scripts_helpers/coding_tools/script_skeleton.py`](/dev_scripts_helpers/coding_tools/script_skeleton.py):
+  - [`/dev_scripts_helpers/coding_tools/script_template.py`](/dev_scripts_helpers/coding_tools/script_template.py):
     a template to write simple scripts you can copy and modify it
   - [`/helpers/hsystem.py`](/helpers/hsystem.py): a set of utilities that make
     simple to run shell commands (e.g., capturing their output, breaking on
     error or not, tee-ing to file, logging, ...)
   - `helpers` has lots of useful libraries
 - The official reference for a script is
-  [`/dev_scripts_helpers/coding_tools/script_skeleton.py`](/dev_scripts_helpers/coding_tools/script_skeleton.py)
+  [`/dev_scripts_helpers/coding_tools/script_template.py`](/dev_scripts_helpers/coding_tools/script_template.py)
   - You can copy this file and change it
   - A simple example is:
     [`/dev_scripts_helpers/git/gup.py`](/dev_scripts_helpers/git/gup.py)