minor improvements

Author: thomasWeise

text/main/classes/dunder/dunder.tex

@@ -512,10 +512,8 @@
 \FloatBarrier%
 \endhsection%
 %
-\hsection{Debugging}%
-%
-\gitPython{\programmingWithPythonCodeRepo}{09_dunder/fraction_decimal_str_err.py}{--args format --labels part_6}{dunder:fraction_decimal_str_err:part_6}{%
-Part~6 of the \pythonil{Fraction} class: Adding a \pythonil{decimal_str} conversation method.}%
+\hsection{Interlude:~Debugging}%
+\label{sec:dunde:debugging}%
 %
 We now want to use mathematics based on our class \pythonil{Fraction} for some \inQuotes{real} computation.
 Remember back in \cref{sec:whileLoop}, we implemented the algorithm of Heron to compute the square root using a \pythonil{while}~loop.
@@ -533,6 +531,9 @@
 Since some fractions, like~$\frac{1}{3}$ and~$\frac{1}{7}$ have never-ending decimal representations, this function needs a parameter \pythonil{max_frac} specifying the maximum number of fractional digits to generate.
 We will set it to 100 by default.
 
+\gitPython{\programmingWithPythonCodeRepo}{09_dunder/fraction_decimal_str_err.py}{--args format --labels part_6}{dunder:fraction_decimal_str_err:part_6}{%
+Part~6 of the \pythonil{Fraction} class: Adding a \pythonil{decimal_str} conversation method.}%
+
 In \cref{lst:dunder:fraction_decimal_str_err:part_6} we present the part of our class \pythonil{Fraction} that contains the code converting the fraction to a decimal string.
 Like all of our code in \pythonil{Fraction}, it takes the straightforward and probably inefficient route.
 The idea is simply to first cut-off the integer part of the fraction and then to produce the fractional digits one-by-one.
@@ -571,7 +572,7 @@
 As last digit, we therefore add \pythonil{80 // 16}, which is~\pythonil{5}.
 This is the last digit, because \pythonil{80 \% 16} is~0.
 Therefore, \pythonil{a == 0} holds after the fifth iteration.
-This makes the first part of the the loop condition \pythonil{a != 0} become \pythonil{False} and the loop terminates.
+This makes the first part of the the loop condition~(\pythonil{a != 0}) become \pythonil{False} and the loop terminates.
 
 At this point, \pythonil{digits == [11, 1, 8, 7, 5]}.
 This is also right, because $\frac{179}{16}=11.1875$.
@@ -596,7 +597,7 @@
 If we only have a single digit, then our fraction is an integer number and we can return it as such.
 Thus, \pythonil{if len(digits) <= 1}, we convert the single digit to a string (after re-inserting the sign).
 
-Otherwise, we need to have \inQuotes{.} after the first number in \pythonil{digits}.
+Otherwise, we need to have a~\inQuotes{.} after the first number in \pythonil{digits}.
 We can use \pythonil{digits.insert(1, ".")} to place it there\pythonIdx{list!insert}.
 In our original example of~$\frac{-179}{16}$, we first had \pythonil{digits == [11, 1, 8, 7, 5]}.
 After this step, we get \pythonil{digits == [11, ".", 1, 8, 7, 5]}.
@@ -684,7 +685,7 @@
 \end{figure}%
 
 We want to investigate this very strange error.
-First, let us repeat the unit tests by also executing them inside \pycharm\ in \cref{fig:dunder:doctests}.
+First, let us repeat the \pglspl{doctest} by also executing them inside \pycharm\ in \cref{fig:dunder:doctests}.
 We open our source file and scroll to our function \pythonil{decimal_str}.
 With a right mouse click, a context menu is opened.
 Here, we then left-click on \menu{Run \inSQuotes{Doctest decimal\_str}}~(\cref{fig:dunder:doctests1}).

text/main/controlFlow/functions/functions.tex

@@ -273,7 +273,7 @@
 \FloatBarrier%
 \endhsection%
 %
-\hsection{Unit Testing}%
+\hsection{Interlude:~Unit Testing}%
 \label{sec:unitTesting}%
 \pythonIdx{function!unit test}%
 \pythonIdx{function!testing}%

text/main/controlFlow/iteration/iteration.tex

@@ -253,7 +253,7 @@
 \FloatBarrier%
 \endhsection%
 %
-\hsection{Brief Interlude: doctests}%
+\hsection{Interlude: doctests}%
 \gitPython{\programmingWithPythonCodeRepo}{07_iteration/list_flatten_iterables.py}{--args format}{iteration:list_flatten_iterables}{%
 A function that flattens \pythonilsIdx{list} and other \pythonilsIdx{Iterable} using list comprehension.}%
 %
@@ -326,6 +326,9 @@
 Since \pglspl{doctest} are usually brief, they are a quick and elegant way to complement more comprehensive unit tests in separate files (see \cref{bp:functionUnitTest}).%
 }%
 %
+While we here execute the \pglspl{doctest} using \pytest\ from the command line, you can also run them directly in~\pycharm.
+We do this later in \cref{sec:dunde:debugging}.%
+%
 \FloatBarrier%
 \endhsection%
 %