moved to new numpy version

Author: thomasWeise

text/main/ecosystem/packages/requirementsFiles/requirementsFiles.tex

@@ -4,7 +4,7 @@
 %
 \gitLoad{lst:packages:requirementstxt}{\programmingWithPythonCodeRepo}{packages/requirements.txt}{}%
 \listingTxt{packages:requirementstxt}{%
-A requirements file demanding that version~\textil{1.26.4} of \numpy\ be installed.}%
+A requirements file demanding that version~\textil{2.5.2} of \numpy\ be installed.}%
 %
 \gitLoad{lst:packages:numpy_user_venv_req_sh}{\programmingWithPythonCodeRepo}{packages/numpy_user_venv_req.sh}{}%
 \gitExecBash{packages:numpy_user_venv_req_sh}{\programmingWithPythonCodeRepo}{packages}{numpy_user_venv_req.sh}
@@ -27,12 +27,12 @@
 \end{sloppypar}%
 %
 \Cref{lst:packages:requirementstxt} gives a trivial example of such a file.
-It contains the line \textil{numpy==1.26.4}.
-This means that \numpy\ of exactly the version~1.26.4 is required for our application.
-Had we written \textil{numpy>=1.26.4}, then a larger version of \numpy\ would also have been OK.
+It contains the line \textil{numpy==2.5.2}.
+This means that \numpy\ of exactly the version~2.5.2 is required for our application.
+Had we written \textil{numpy>=2.5.2}, then a larger version of \numpy\ would also have been OK.
 The other operators, \textil{>}, \textil{<}, and~\textil{<=} can be used as well and have their natural corresponding meaning.
-If we had wanted, we could have written \textil{matplotlib} in the second line of our \textil{requirements.txt} file, which would then have meant that, besides \numpy\ of version~\textil{1.26.4}, the package \matplotlib\ is needed as well.
-Writing only \textil{matplotlib} would be interpreted as \inQuotes{find the highest version of \matplotlib\ that is compatible with \numpy\ version~1.26.4.}
+If we had wanted, we could have written \textil{matplotlib} in the second line of our \textil{requirements.txt} file, which would then have meant that, besides \numpy\ of version~\textil{2.5.2}, the package \matplotlib\ is needed as well.
+Writing only \textil{matplotlib} would be interpreted as \inQuotes{find the highest version of \matplotlib\ that is compatible with \numpy\ version~2.5.2.}
 But we only need one package, \numpy, so our file just has a single line.
 
 In \cref{lst:packages:numpy_user_venv_req_sh}, we present a version of the script that we used to set up a virtual environment and run our two-line \numpy\ program under \ubuntu\ \linux~(see \cref{lst:packages:numpy_user_venv_req_sh}.)

text/main/ecosystem/packages/venvAndPycharm/venvAndPycharm.tex

@@ -30,7 +30,7 @@
 \floatSep%
 %
 \subfloat[][%
-It contains the one line \textil{numpy==1.26.4}, which means that our project requires \numpy\ in version~1.26.4.%
+It contains the one line \textil{numpy==2.5.2}, which means that our project requires \numpy\ in version~2.5.2.%
 \label{fig:venvPycharm4}%
 ]{\tightbox{\includegraphics[width=0.48\linewidth]{\currentDir/venvPycharm4}}}%
 %
@@ -99,7 +99,7 @@
 Notice that you could as well create an empty project and copy the files there.
 
 We click on \textil{requirements.txt} and it opens in~\cref{fig:venvPycharm4}.
-Indeed, the file prescribes a single requirement, \numpy\ in version~1.26.4.
+Indeed, the file prescribes a single requirement, \numpy\ in version~2.5.2.
 
 When we click on the file \programUrl{packages:numpy_user} to open it in~\cref{fig:venvPycharm5}, we notice a yellow bar at the top of the file's contents.
 This bar tells us that the required package \numpy\ is missing.
@@ -110,7 +110,7 @@
 Either way, we accept the choice to install the requirement.
 
 In \cref{fig:venvPycharm6}, we are informed that the installation was successful.
-The small overlay also tells us that \numpy\ was installed in version~1.26.4, as prescribed by the \textil{requirements.txt} file.
+The small overlay also tells us that \numpy\ was installed in version~2.5.2, as prescribed by the \textil{requirements.txt} file.
 At the time of this writing, \numpy\ is already out at version~2.2.1, which would have been used if we had just installed it without version specification.
 So this confirms that, indeed, our \textil{requirements.txt} is used.
 We also can see that the red underline under \pythonilIdx{numpy} that was present in \cref{fig:venvPycharm5} is now gone in \cref{fig:venvPycharm6}, because now the package and corresponding modules can be loaded without error.