using newest latexgit_py version

Author: thomasWeise

bibliography/bibliography.bib

@@ -16,3 +16,26 @@ @string { summer
 @string { autumn = "{\bibstring{autumn}}" }
 @string { winter = "{\bibstring{winter}}" }
 
+
+%% locations
+@string { l_cambridge_uk = "{Cambridge, England, UK}" }
+
+
+%% publishers
+@string { p_cambridge_uni_press_ass = "{Cambridge University Press \& Assessment}" }
+
+
+%% publisher addresses
+@string { pa_cambridge_uni_press_ass = l_cambridge_uk }
+
+
+%% contents
+@incollection{CDE2024PMOPIE,
+ title = {programming: Meaning of \emph{programming} in English},
+ booktitle = {Cambridge Dictionary English~({UK})},
+ publisher = p_cambridge_uni_press_ass,
+ address = pa_cambridge_uni_press_ass,
+ date = {2024-06},
+ url = {https://dictionary.cambridge.org/dictionary/english/programming},
+ urldate = {2024-06-17}
+}

make.sh

@@ -15,17 +15,19 @@ echo "$(date +'%0Y-%0m-%0d %0R:%0S'): We are working in directory: '$currentDir'
 scriptDir="$currentDir/scripts"
 echo "$(date +'%0Y-%0m-%0d %0R:%0S'): The script directory is '$scriptDir'."
 
-echo "$(date +'%0Y-%0m-%0d %0R:%0S'): First we delete all left over data."
+echo "$(date +'%0Y-%0m-%0d %0R:%0S'): We delete all left over data."
 rm "book.pdf" || true
 rm -rf "$currentDir/website" || true
 
-echo "$(date +'%0Y-%0m-%0d %0R:%0S'): First, we need to setup a virtual environment in a temp directory."
+echo "$(date +'%0Y-%0m-%0d %0R:%0S'): We setup a virtual environment in a temp directory."
 tempDir="$(mktemp -d)"
 echo "$(date +'%0Y-%0m-%0d %0R:%0S'): Got temp dir '$tempDir', now creating environment in it."
 python3 -m venv "$tempDir"
 echo "$(date +'%0Y-%0m-%0d %0R:%0S'): Activating virtual environment in '$tempDir'."
 . "$tempDir/bin/activate"
-echo "$(date +'%0Y-%0m-%0d %0R:%0S'): Initialization: We install all required Python packages from requirements.txt to virtual environment in '$tempDir'."
+export PYTHON_INTERPRETER="$tempDir/bin/python3"
+echo "$(date +'%0Y-%0m-%0d %0R:%0S'): Setting python interpreter to '$PYTHON_INTERPRETER'."
+echo "$(date +'%0Y-%0m-%0d %0R:%0S'): We install all required Python packages from requirements.txt to virtual environment in '$tempDir'."
 pip install --no-input --timeout 360 --retries 100 -r requirements.txt
 echo "$(date +'%0Y-%0m-%0d %0R:%0S'): Finished installing the requirements, now printing all installed packages."
 pip freeze

requirements.txt

@@ -6,7 +6,7 @@
 # You can find it at https://thomasweise.github.io/latexgit_py,
 # https://github.com/thomasWeise/latexgit_py, or at
 # https://pypi.org/project/latexgit.
-latexgit == 0.8.12
+latexgit == 0.8.13
 
 # minify_html is needed to minify html output.
 minify_html == 0.15.0

scripts/pdflatex.sh

@@ -28,7 +28,15 @@ echo "$(date +'%0Y-%0m-%0d %0R:%0S'): We will use ${texProgram[@]} to compile th
 bibProgram="$(readlink -f "$(which biber)")"
 echo "$(date +'%0Y-%0m-%0d %0R:%0S'): We will use '$bibProgram' to process bibliography files."
 "$bibProgram" --version
-latexGitProgram=("$(readlink -f "$(which python3)")" "-m" "latexgit.aux")
+
+if [[ $(declare -p PYTHON_INTERPRETER) == declare\ ?x* ]]; then
+  echo "Found python interpreter as: '$PYTHON_INTERPRETER'"
+else
+  export PYTHON_INTERPRETER="$(readlink -f "$(which python3)")"
+  echo "Setting up python interpreter as '$PYTHON_INTERPRETER'."
+fi
+
+latexGitProgram=("$PYTHON_INTERPRETER" "-m" "latexgit.aux")
 echo "$(date +'%0Y-%0m-%0d %0R:%0S'): We will use latexgit like ${latexGitProgram[@]}."
 ${latexGitProgram[@]} --version
 makeIndexProgram="$(readlink -f "$(which makeindex)")"

text/main/introduction/introduction.tex

@@ -1,7 +1,56 @@
 \hsection{}%
 \hsection{Introduction}%
 %
-This is work in progress.
+In this book, we want to learn \emph{program}.
+Programming is often described as \emph{the activity or job of writing computer programs}~\cite{CDE2024PMOPIE}.
+However, this is only \emph{one} aspect of it.
+Actually, in the real world, the act of programming is not just the activity of writing some code.
+Imagine the following scenario:
+
+A person, say your future boss, comes to you and says:
+\inQuotes{Write a program that solves this task here.}
+Then you write the program and give here the text file.
+Everybody is happy, the problem is solved.
+
+Sounds kind of unrealistically, right?
+You get a task and just write the program that solves it.
+Is it that easy?
+Well, OK, you can reasonably expect that you learn how to do that in this course.
+We will teach you \texttt{Python} programming.
+So you expect to learn how to translate some kind of specification into code.
+Fine.
+
+But how does your boss know that the program you give her will do the job?
+And that it will do so reliably?
+What sort of confidence can she have into the assumption that you won't be making any errors?
+
+And what if your program is not just a single-use, stand-alone kind of program?
+What if it is part of some sort of software ecosystem?
+What if other programs need to use/run it?
+Maybe it can access some sort of sensor measuring something, or maybe it can convert data from one file format to another one.
+Then, other programmers may need to be able to at least understand how to correctly run the program and what kind of input and output data it will expect or produce, respectively.
+
+What if this program is going to be needed for the next ten or so years?
+Maybe it could be necessary to add new functionality?
+Maybe some of the libraries you use get outdated and need to be replaced?
+There are several reasonable situations in which a totally different person may need to work, read, modify, and improve \emph{your} code.
+
+Or maybe you are a researcher, using \texttt{Python} to implement some algorithm and to run an experiment.
+In order to make your experiments and results replicable, you would probably want to publish your algorithm implementation together with the results.
+This only makes sense if your code is at least a bit readable.
+
+All of these things need to be considered when we learn how to program.
+And in typical courses, they are not.
+In a typical course, you learn how to write a small program that solves a certain task.
+The task is usually simple, so the teachers are able to read your code even if you have ugliest style imaginable.
+Also, nobody is ever going to look at or use the programs you write as your homework again.
+So one of the above really matters.
+But in reality, things are not always simple.
+
+One may  hope that, as one of the very first things, surgery students in medical school are taught to wash their hands before performing surgery.
+Hence, we will teach you how to write clean, well-documented, and properly tested programs.
+Right from the start.
+Such that all of your code will be reusable, readable, clear, clean, and beautiful.%
 %
 \endhsection\endhsection%
 %