many improvements, especially with regard to loops

Author: thomasWeise

LICENSE.md

@@ -13,6 +13,7 @@ The list of files not under the CC BY‑NC‑SA 4.0 license bu
     - text/main/introduction/pythonLogo.svg
 + all screenshots from websites
 + The illustration of LIU Hui (刘徽) in file "text/main/basics/variables/assignment/liu_hui.jpg" is from Wenqi Ying (应雯棋), editor. Commemoration of Ancient Chinese Mathematical Master Liu Hui for his Timeless Influence on Mathematics and Civilizational Exchange. [Issue 48 of CAST Newsletter](https://english.cast.org.cn/cms_files/filemanager/1941250207/attach/202412/8f23655a82364d19ad7874eb37b23035.pdf). China, Beijing (中国北京市): 中国科学技术协会 (China Association for Science and Technology, CAST), 2024. Permission was granted to include it in this material, but the copyright remains with CAST.
++ The illustration of Hero(n) of Alexandria in file "text/main/controlFlow/loops/heronOfAlexandria.jpg" is taken from the article "[The Ancient Greek Who Invented the World's First Steam Turbine](https://greekreporter.com/2023/12/13/ancient-greek-world-first-steam-turbine)", where its caption states *Heron of Alexandria. Codex of Saint Gregory Nazianzenos. Greek manuscript of the ninth century. Public Domain*.
 
 
 ## creative commons

README.md

@@ -41,11 +41,13 @@ Die Slides zum Kurs in deutscher Sprache können unter <https://thomasweise.gith
 16. [Gleichheit und Identität](https://thomasweise.github.io/programmingWithPythonSlidesDE/16_gleichheit_und_identität.pdf)
 17. [Listen](https://thomasweise.github.io/programmingWithPythonSlidesDE/17_listen.pdf)
 18. [Zwischenspiel: Der Linter Ruff](https://thomasweise.github.io/programmingWithPythonSlidesDE/18_ruff.pdf)
-19. [Tupels](https://thomasweise.github.io/programmingWithPythonSlidesDE/19_tupels.pdf)
+19. [Tupel](https://thomasweise.github.io/programmingWithPythonSlidesDE/19_tupel.pdf)
 20. [Mengen](https://thomasweise.github.io/programmingWithPythonSlidesDE/20_mengen.pdf)
 21. [Dictionaries bzw. Hash Maps](https://thomasweise.github.io/programmingWithPythonSlidesDE/21_dictionaries.pdf)
 22. [Alternativen mit `if`](https://thomasweise.github.io/programmingWithPythonSlidesDE/22_alternativen_mit_if.pdf)
 23. [Schleifen mit `for`](https://thomasweise.github.io/programmingWithPythonSlidesDE/23_schleifen_mit_for.pdf)
+24. [`enumerate` und Zwischenspiel: Pylint](https://thomasweise.github.io/programmingWithPythonSlidesDE/24_enumerate_und_pylint.pdf)
+25. [Schleifen mit `while`](https://thomasweise.github.io/programmingWithPythonSlidesDE/25_schleifen_mit_while.pdf)
 
 
 ### 2.3. The Slides in English
@@ -82,6 +84,7 @@ The list of files not under the CC&nbsp;BY&#8209;NC&#8209;SA&nbsp;4.0 license bu
     - text/main/introduction/pythonLogo.svg
 + all screenshots from websites
 + The illustration of LIU Hui (刘徽) in file "text/main/basics/variables/assignment/liu_hui.jpg" is from Wenqi Ying (应雯棋), editor. Commemoration of Ancient Chinese Mathematical Master Liu Hui for his Timeless Influence on Mathematics and Civilizational Exchange. [Issue 48 of CAST Newsletter](https://english.cast.org.cn/cms_files/filemanager/1941250207/attach/202412/8f23655a82364d19ad7874eb37b23035.pdf). China, Beijing (中国北京市): 中国科学技术协会 (China Association for Science and Technology, CAST), 2024. Permission was granted to include it in this material, but the copyright remains with CAST.
++ The illustration of Hero(n) of Alexandria in file "text/main/controlFlow/loops/heronOfAlexandria.jpg" is taken from the article "[The Ancient Greek Who Invented the World's First Steam Turbine](https://greekreporter.com/2023/12/13/ancient-greek-world-first-steam-turbine)", where its caption states *Heron of Alexandria. Codex of Saint Gregory Nazianzenos. Greek manuscript of the ninth century. Public Domain*.
 
 You can download its newest version of the course material from <https://thomasweise.github.io/databases>.
 This version may change since this course and book both are work in progress.

bookbase

@@ -69,7 +69,7 @@
 \Cref{lst:bash:pylint} offers exactly the same functionality for \pylint.
 It checks if this tool is installed and installs it if not.
 It then applies \pylint\ to a the selected set of files, using a reasonable default configuration.
-\Cref{exec:loops:for_loop_no_enumerate:pylint} is an example of the output of this \pgls{linter}.
+\Cref{exec:loops:for_loop_no_enumerate_1:pylint} is an example of the output of this \pgls{linter}.
 
 \Cref{lst:bash:pytest} is similarly structured, but instead of performing \emph{static} code analysis, it executes \pgls{unitTest} cases.
 The directory and list of \python\ files with the test cases are provided as command line arguments.

text/back/scripts.tex

@@ -11,7 +11,7 @@
 %
 Recently, we learned that static code analysis tools can help us to discover subtle problems in our programs.
 Obviously, when dealing with more complex datastructures like lists, there are also more potential problems, more mistakes that one could make.
-Let us look at the very short example program \textil{lists_error.py} in \cref{lst:lists:lists_error}.
+Let us look at the very short example program \programUrl{lists:lists_error} in \cref{lst:lists:lists_error}.
 The program consists of only two lines, \pythonil{my_list: list[str] = list([1, 2, 3])} and \pythonil{print(my_list)}.
 It does not have any \emph{error} in the strict sense.
 We can execute it just fine and it will produce the output \textil{[1, 2, 3]} as shown in \cref{exec:lists:lists_error}.
@@ -48,7 +48,7 @@
 \listingToolOutput{lists:lists_error:ruff}{%
 The results of linting with \ruff\ of the program given in \cref{lst:lists:lists_error}. (We used the script given in \cref{lst:bash:ruff} on \cpageref{lst:bash:ruff} to apply \ruff.)}%
 %
-Let us apply \ruff\ to the program \textil{lists_error.py} given in \cref{lst:lists:lists_error}.
+Let us apply \ruff\ to the program \programUrl{lists:lists_error} given in \cref{lst:lists:lists_error}.
 This can be done by executing the command \bashil{ruff check myfile.py}, where \textil{myfile.py} is the file to be checked~(you can also specify a directory).
 \ruff\ has many additional parameters, which are explained at~\cite{PSF:TPPIP:R,M2022RAEFPLACFWIR}.
 For example, if we want to analyze our code with respect to version~3.12 of \python, we would specify the command line argument~\textil{--target-version py312}.

text/main/basics/collections/ruff/ruff.tex

@@ -30,7 +30,7 @@
 How can we deal with the fact that we cannot represent arbitrary fractional numbers exactly even in typical everyday cases like~\numberPi\ and~\numberE?
 How can we deal with the situation that real numbers exist as big as~$10^{300}$ and as small as~$10^{-300}$?
 With \pythonilIdx{float}, \python\ offers us one type for fractional numbers.
-This datatype represents numbers usually in the same internal structure as \pythonils{double} in the \pgls{C}~programming language~\cite{PSF:P3D:TPSL:NTIFC} -- it is based on the 64~bit IEEE~Standard 754 floating point number layout~\cite{IEEE2019ISFFPA,H1997IS7FPN}.
+This datatype represents numbers usually in the same internal structure as \pythonils{double} in the \pgls{C}~programming language~\cite{PSF:P3D:TPSL:NTIFC} -- it is based on the 64~bit IEEE~Standard 754 floating point number layout~\cite{IEEE2019ISFFPA,H1997IS7FPN,G1991WECSSKAFPA}.
 The idea behind this standard is exactly to be able to represent both very large numbers, like~$10^{300}$ and very small numbers, like~$10^{-300}$, while accepting that we cannot exactly represent~$10^{300}+10^{-300}$.
 In order to achieve this, the 64~bits are divided into three pieces, as illustrated in \cref{fig:floatIEEEStructure}.
 %
@@ -61,6 +61,7 @@
 \end{sloppypar}%
 %
 Luckily, you will never really need to know these exact information in your day-to-day programming work.
+There also exist many different formats of floating point numbers, using different numbers of bits for significand and exponent~\cite{IEEE2019ISFFPA,G1991WECSSKAFPA}.
 The important thing to remember is:
 Floating point numbers~(\pythonils{float}) can represent a wide range of different values.
 Their range is large but still limited.
@@ -425,7 +426,7 @@
 Or \pythonilIdx{nan}, which stands for, well, Not a Number\pythonIdx{Not a Number}.
 
 \pythonilIdx{nan} means that the result of a computation is neither a finite number or infinite.
-It is the result of shenanigans such as \pythonil{inf - inf} or \pythonil{inf / inf} or \pythonil{0 * inf}.
+It is the result of shenanigans such as \pythonil{inf - inf} or \pythonil{inf / inf} or \pythonil{0 * inf}~\cite{G1991WECSSKAFPA}.
 A \pythonilIdx{nan} value anywhere in a computation infects the result of the computation to also become \pythonilIdx{nan}.
 \pythonil{nan + 1} remains \pythonilIdx{nan} and so does \pythonil{nan + inf}.
 

text/main/basics/simpleDataTypesAndOperations/float/float.tex

@@ -96,37 +96,37 @@
 \centering%
 %
 \subfloat[][%
-The file \textil{assignment.py} opened in \pycharm.%
+The file \programUrl{variables:assignment} opened in \pycharm.%
 \label{fig:assignmentPyCharm1}%
 ]{%
 \tightbox{\includegraphics[width=0.49\linewidth]{\currentDir/assignmentPyCharm1}}%
 }%
 \hfill%
 %
 \subfloat[][%
-Left-clicking on \menu{Run `assignment'} in the pop-up menu after right-clicking on \textil{assignment.py}, or directly pressing \keys{\ctrl+\shift+F10}, to run the program.%
+Left-clicking on \menu{Run `assignment'} in the pop-up menu after right-clicking on \programUrl{variables:assignment}, or directly pressing \keys{\ctrl+\shift+F10}, to run the program.%
 \label{fig:assignmentPyCharm2}%
 ]{%
 \tightbox{\includegraphics[width=0.49\linewidth]{\currentDir/assignmentPyCharm2}}%
 }%
 \\%
 %
 \subfloat[][%
-The output of the program \textil{assignment.py} in \pycharm.%
+The output of the program \programUrl{variables:assignment} in \pycharm.%
 \label{fig:assignmentPyCharm3}%
 ]{%
 \tightbox{\includegraphics[width=0.7\linewidth]{\currentDir/assignmentPyCharm3}}%
 }%
 \\%
 %
 \subfloat[][%
-The output of the program \textil{assignment.py} in the \ubuntu\ \pgls{terminal} (which you can open via~\ubuntuTerminal).%
+The output of the program \programUrl{variables:assignment} in the \ubuntu\ \pgls{terminal} (which you can open via~\ubuntuTerminal).%
 \label{fig:assignmentTerminal}%
 ]{%
 \includegraphics[width=0.7\linewidth]{\currentDir/assignmentTerminal}%
 }%
 %
-\caption{Running the program \textil{assignment.py} from \cref{lst:variables:assignment} in \pycharm~(\cref{fig:assignmentPyCharm1,fig:assignmentPyCharm2,fig:assignmentPyCharm3}) or the \ubuntu\ \pgls{terminal}~(\cref{fig:assignmentTerminal}).}%
+\caption{Running the program \programUrl{variables:assignment} from \cref{lst:variables:assignment} in \pycharm~(\cref{fig:assignmentPyCharm1,fig:assignmentPyCharm2,fig:assignmentPyCharm3}) or the \ubuntu\ \pgls{terminal}~(\cref{fig:assignmentTerminal}).}%
 \label{fig:variables:assignment}%
 \end{figure}%
 %
@@ -172,18 +172,18 @@
 (Do you remember a method, to get this output even more easily?)%
 \end{sloppypar}%
 %
-This first program is stored in a file named~\textil{assignment.py}.
+This first program is stored in a file named~\programUrl{variables:assignment}.
 To execute it, you have two choices:
 You can do this in the \pgls{terminal} or using \pycharm.%
 %
 \begin{sloppypar}%
 Under \ubuntu\ \linux, you open the \pgls{terminal} by pressing \ubuntuTerminal, under \microsoftWindows\ you instead \windowsTerminal.
-Then you enter the folder where the program \textil{assignment.py} is stored using the command~\bashil{cd}.
+Then you enter the folder where the program \programUrl{variables:assignment} is stored using the command~\bashil{cd}.
 Then you would execute the command~\bashil{python3 assignment.py} to run the \python\ interpreter, as illustrated in \cref{fig:assignmentTerminal}.%
 \end{sloppypar}%
 %
 Alternatively, you can open the program file in \pycharm\ \pgls{ide}, as sketched in \cref{fig:assignmentPyCharm1}.
-You would then right-click on the file \textil{assignment.py} in the project tree view.
+You would then right-click on the file \programUrl{variables:assignment} in the project tree view.
 In the popup-menu that opens, you would left-click on \menu{Run `assignment'} as shown in \cref{fig:assignmentPyCharm2}.
 As a shortcut, you can also simply press~\keys{\ctrl+\shift+F10}.
 Either way, \pycharm\ will run the program and the output appears in \cref{fig:assignmentPyCharm3}.
@@ -361,7 +361,7 @@
 Now that we have learned some programming, we do no longer need to type the numbers and computation steps into a calculator.
 We also do not need to use \python\ as calculator.
 Instead, we can enter all the commands needed for the computation into a program file.
-We will call it~\textil{pi_liu_hui.py}, as illustrated in \cref{lst:variables:pi_liu_hui}.
+We will call it~\programUrl{variables:pi_liu_hui}, as illustrated in \cref{lst:variables:pi_liu_hui}.
 
 We begin by setting the initial number of edges \pythonil{e = 6} and the initial side length of the $e$\nobreakdashes-gon to \pythonil{s = 1}, because we still keep with the choice of~$\liuhuir=1$.
 In each iteration of the approximation, we simply set \pythonil{e *= 2}\pythonIdx{*=}, which is equivalent to \pythonil{e = e * 2}, to double the number of edges.
@@ -377,7 +377,7 @@
 
 For your convenience, we also showed the results when executing the program in \pycharm\ or the \ubuntu\ \pgls{terminal} in \cref{fig:variables:liuHuiPi}.
 To open a \pgls{terminal} under \ubuntu\ \linux, you would press~\ubuntuTerminal, whereas under \microsoftWindows, you~\windowsTerminal.
-With the command \bashil{cd}, you would enter the directory where our program \textil{pi_liu_hui.py} is located.
+With the command \bashil{cd}, you would enter the directory where our program \programUrl{variables:pi_liu_hui} is located.
 You would then type in \bashil{python3 pi_liu_hui.py} and hit~\keys{\enter}.
 As you can see in \cref{fig:liuHuiPiTerminal}, you will get the same output as given in \cref{exec:variables:pi_liu_hui}.
 

text/main/basics/variables/assignment/assignment.tex

@@ -9,7 +9,7 @@
 \centering%
 %
 \subfloat[][%
-We run the program \textil{assignment_wrong.py} given in \cref{lst:variables:assignment_wrong} in the \pycharm\ \pgls{ide} by clicking on the \pycharmRun\ button or by pressing~\keys{\shift+F10}.%
+We run the program \programUrl{variables:assignment_wrong} given in \cref{lst:variables:assignment_wrong} in the \pycharm\ \pgls{ide} by clicking on the \pycharmRun\ button or by pressing~\keys{\shift+F10}.%
 \label{fig:errorsInIde01runProgram}%
 ]{\tightbox{\includegraphics[width=0.9\linewidth]{\currentDir/errorsInIde01runProgram}}}%
 %
@@ -19,7 +19,7 @@
 The output in the run window is the same as given in \cref{exec:variables:assignment_wrong}. %
 It is the \emph{first} way to find out what went wrong. %
 It tells us what went wrong and even suggests how to fix it:~\emph{\pythonilIdx{NameError}: name \inSQuotes{\pythonil{intvar}} is not defined. Did you mean: \inSQuotes{\pythonil{int_var}}?} %
-It also tells us the exact file and line where the error occurred, namely in line~12 of file \textil{assignment_wrong.py}.%
+It also tells us the exact file and line where the error occurred, namely in line~12 of file \programUrl{variables:assignment_wrong}.%
 \label{fig:errorsInIde02exception}%
 ]{\tightbox{\includegraphics[width=0.9\linewidth]{\currentDir/errorsInIde02exception}}}%
 %
@@ -115,12 +115,12 @@
 %
 %
 \hsection{Finding the Error by using the Program Output and Exceptions}%
-In \cref{lst:variables:assignment_wrong}, we prepared program \textil{assignment_wrong.py}, a variant of \textil{assignment.py}~(\cref{lst:variables:assignment}) with an error.
+In \cref{lst:variables:assignment_wrong}, we prepared program \programUrl{variables:assignment_wrong}, a variant of \programUrl{variables:assignment}~(\cref{lst:variables:assignment}) with an error.
 For the sake of the example, let us assume that the programmer made a typo in line~12 of the program:
 They misspelled \pythonil{int_var} as \pythonil{intvar}.
 Executing the program with the error leads to the output given in \cref{exec:variables:assignment_wrong}.
 
-We can also open the program \textil{assignment_wrong.py} given in the \pycharm\ \pgls{ide}.
+We can also open the program \programUrl{variables:assignment_wrong} given in the \pycharm\ \pgls{ide}.
 We execute this program manually by clicking on the \pycharmRun\ button or by pressing~\keys{\shift+F10} in \cref{fig:errorsInIde01runProgram}.
 As you can see, the output in the run window is the same as given in \cref{exec:variables:assignment_wrong}~(\cref{fig:errorsInIde02exception}).
 
@@ -133,7 +133,7 @@
 
 The \python\ interpreter then checks whether some similar name exists.
 It found that there is a variable named \pythonil{int_var}.
-Even more, it also tells us the exact file and line where the error occurred, namely in line~12 of file \textil{assignment_wrong.py}!
+Even more, it also tells us the exact file and line where the error occurred, namely in line~12 of file \programUrl{variables:assignment_wrong}!
 With this information, we have a good chance of finding the mistake.
 
 The so-called \pythonilIdx{Exception} \pgls{stackTrace} that it prints to \pgls{stderr} thus not just tells us that there was an error.