Deployed 04f087f with MkDocs version: 1.6.0

index.html

@@ -197,5 +197,5 @@ <h1 id="installation-guide">Installation Guide</h1>
 
 <!--
 MkDocs version : 1.6.0
-Build Date UTC : 2024-08-15 12:04:09.650848+00:00
+Build Date UTC : 2024-08-20 09:22:28.420825+00:00
 -->

python-more/index.html

@@ -157,7 +157,7 @@ <h1 id="additional-python-packages">Additional Python packages</h1>
 </code></pre>
 <p>Press enter to accept the proposed package plan with 'y' and <code>return</code>.</p>
 <p>This command installs those two packages into the default (base) environment. It is fine, as we would like those to be shared across all environments we later create. However, it is generally not the case, as we want dependencies for our different projects well separated. For example, packages for this course should be wholly independent from packages you are using to write a paper. The next command creates a <code>conda</code> environment called <code>pp4rs</code> and installs all the packages required for the course. It might take a while.</p>
-<pre><code class="language-bash">    conda env create -f https://pp4rs.github.io/2024-uzh-installation-guide/assets/pp4rs-environment.yml
+<pre><code class="language-bash">    conda env create -f https://pp4rs.github.io/2024-uzh-installation-guide/assets/pp4rs_environment.yml
 </code></pre>
 <p>Generally, you should have such a file for each of your projects in order to easily reproduce the environment it was built in any time in the future.</p>
 <div class="admonition tip">