using new latexgit_py version that cleans paths in execution outputs

Author: thomasWeise

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.23
+latexgit == 0.8.25
 
 # minify_html is needed to minify html output.
 minify_html == 0.15.0

text/main/basics/collections/tuples/tuples.tex

@@ -112,7 +112,7 @@
 This is an exception which, unless properly caught and handled, will terminate the program immediately.
 \Cref{exec:tuples:tuples_3} shows us this.
 While the first two \pythonilIdx{print} commands still succeed, the program crashes when we lay our hands on the tuple directly.
-The \python\ interpreter is kind enough to print the error as well as where it happened.
+The \python\ interpreter is kind enough to print the error as well as where it happened (see also later in \cref{sec:exceptions}).
 This would help the programmer to find the problem.
 
 Had the programmer used \mypy\ to check the code before running it, however, they would have found the error already.

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

@@ -365,7 +365,7 @@
 Trying to do that with a ten times larger number, i.e., computing \pythonil{17_976_931_348_623_157 * 10 ** 293 * 1.0} leads to an exception:
 The output is \pythonil{OverflowError: int too large to convert to float}\pythonIdx{OverflowError}.
 An exception terminates the current flow of execution and signals an error.
-We will learn later what exceptions actually are and how to handle them properly.
+Later in \cref{sec:exceptions}, we will learn what \pythonilsIdx{Exception} actually are and how to handle them properly.
 
 The important thing to realize is that an overflow of a \pythonilIdx{float} may either lead to the \pythonilIdx{inf} value or to an error that stops your computation from continuing.
 As another example, let us again import the natural logarithm function \pythonilIdx{log} and the Euler's constant~\pythonilIdx{e} from the \pythonilIdx{math} module by doing \pythonil{from math import e, log}\pythonIdx{from}\pythonIdx{math}\pythonIdx{import}.

text/main/controlFlow/exceptions/exceptions.tex

@@ -172,7 +172,9 @@
 
 It begins with the line \textil{Traceback (most recent call last):}.
 In the first line following this text, the source code file and the index of the line in that file where the \pythonilIdx{Exception} was originally raised are printed.
-The full path of the file may look a bit strange, since this book is compiled by a \github\ Action~\cite{C2024GA}, but at least the last part of the path, \textil{06_exceptions/use_sqrt_raise.py} clearly points out the calling program as the culprit \cref{lst:exceptions:use_sqrt_raise}.
+Notice that the actual path to the files will be different depending on where the source code of the examples is located.
+We replaced the variable part of the path with~\inQuotes{\{\dots\}}.
+The remaining part of the path, \textil{06_exceptions/use_sqrt_raise.py}, clearly points out the calling program as the culprit \cref{lst:exceptions:use_sqrt_raise}.
 Indeed, the following line of text identifies that instruction in \cref{lst:exceptions:use_sqrt_raise} that caused the error and even marks the offending function invocation by underlining it with \textil{{^}{^}{^}{^}{^}{^}{^}{^}{^}{^}{^}{^}}.
 Below that, we get to see the context of our \pythonil{sqrt} function:
 First, the path to its module is given (ending in \textil{06_exceptions/sqrt_raise.py}) and it is pointed out that the \pythonilIdx{Exception} was raised in line~15.