Skip to content

Commit 13b92e8

Browse files
committed
Website build
1 parent fde6d3a commit 13b92e8

File tree

3 files changed

+15
-15
lines changed

3 files changed

+15
-15
lines changed

1_introduction.html

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ <h3><span class="section-number">1.1.1. </span>Python versions<a class="headerli
141141
references in this book are to that version.</p>
142142
<p>Within Python 3, there is a minor version release approximately every year.
143143
Once released, this receives security updates for 5 years. At the time of
144-
writing, Python 3.11 is the newest release version, and Python 3.8 is the
144+
writing, Python 3.12 is the newest release version, and Python 3.9 is the
145145
oldest version that still receives security fixes. The user-facing differences
146146
between minor Python versions are usually fairly minimal, so for the purposes
147147
of this book it doesn’t matter which of the currently supported versions of
@@ -161,20 +161,20 @@ <h3><span class="section-number">1.1.1. </span>Python versions<a class="headerli
161161
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">&gt; py --version</span>
162162
</pre></div>
163163
</div>
164-
<p>On the author’s computer, this prints <code class="xref py py-obj docutils literal notranslate"><span class="pre">Python</span> <span class="pre">3.11.4</span></code>, which is the version of
164+
<p>On the author’s computer, this prints <code class="xref py py-obj docutils literal notranslate"><span class="pre">Python</span> <span class="pre">3.12.6</span></code>, which is the version of
165165
Python I expect to be using. This means I can launch Python on Windows using
166166
just <code class="xref py py-obj docutils literal notranslate"><span class="pre">py</span></code>. If it printed a different version, then I could attempt to force it
167167
to use the version I want like this:</p>
168-
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">&gt; py -3.11 --version</span>
168+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">&gt; py -3.12 --version</span>
169169
</pre></div>
170170
</div>
171171
<p>If that fails, then there is an issue with your Python documentation and you
172172
need to go back to the start of this section to work out how to install the
173173
right version.</p>
174174
<p>On Mac or Linux, the safest way to ensure that you are running the right
175-
version of Python is to use the full version number, e.g. <code class="xref py py-obj docutils literal notranslate"><span class="pre">python3.11</span></code>. You can
175+
version of Python is to use the full version number, e.g. <code class="xref py py-obj docutils literal notranslate"><span class="pre">python3.12</span></code>. You can
176176
check this with, for example:</p>
177-
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>python3.11<span class="w"> </span>--version
177+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>python3.12<span class="w"> </span>--version
178178
</pre></div>
179179
</div>
180180
<p>If this fails, then the relevant Python version isn’t (correctly) installed and
@@ -232,11 +232,11 @@ <h3><span class="section-number">1.2.2. </span>Creating the venv<a class="header
232232
want this to be short, but distinctive enough that you know which venv you are
233233
using. For example, to create a venv
234234
called <code class="xref py py-obj docutils literal notranslate"><span class="pre">PoP_venv</span></code> on Windows, you would type:</p>
235-
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">&gt; py -3.11 -m venv PoP_venv</span>
235+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">&gt; py -3.12 -m venv PoP_venv</span>
236236
</pre></div>
237237
</div>
238238
<p>while on Mac or Linux you would type:</p>
239-
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>python3.11<span class="w"> </span>-m<span class="w"> </span>venv<span class="w"> </span>PoP_venv
239+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="gp">$ </span>python3.12<span class="w"> </span>-m<span class="w"> </span>venv<span class="w"> </span>PoP_venv
240240
</pre></div>
241241
</div>
242242
<p>If you’re using a different version of Python then modify the command according

_sources/1_introduction.rst.txt

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ references in this book are to that version.
114114

115115
Within Python 3, there is a minor version release approximately every year.
116116
Once released, this receives security updates for 5 years. At the time of
117-
writing, Python 3.11 is the newest release version, and Python 3.8 is the
117+
writing, Python 3.12 is the newest release version, and Python 3.9 is the
118118
oldest version that still receives security fixes. The user-facing differences
119119
between minor Python versions are usually fairly minimal, so for the purposes
120120
of this book it doesn't matter which of the currently supported versions of
@@ -140,26 +140,26 @@ default:
140140
141141
> py --version
142142
143-
On the author's computer, this prints `Python 3.11.4`, which is the version of
143+
On the author's computer, this prints `Python 3.12.6`, which is the version of
144144
Python I expect to be using. This means I can launch Python on Windows using
145145
just `py`. If it printed a different version, then I could attempt to force it
146146
to use the version I want like this:
147147

148148
.. code-block:: console
149149
150-
> py -3.11 --version
150+
> py -3.12 --version
151151
152152
If that fails, then there is an issue with your Python documentation and you
153153
need to go back to the start of this section to work out how to install the
154154
right version.
155155

156156
On Mac or Linux, the safest way to ensure that you are running the right
157-
version of Python is to use the full version number, e.g. `python3.11`. You can
157+
version of Python is to use the full version number, e.g. `python3.12`. You can
158158
check this with, for example:
159159

160160
.. code-block:: console
161161
162-
$ python3.11 --version
162+
$ python3.12 --version
163163
164164
If this fails, then the relevant Python version isn't (correctly) installed and
165165
you will need to use a different version, or install it.
@@ -239,13 +239,13 @@ called `PoP_venv` on Windows, you would type:
239239

240240
.. code-block:: console
241241
242-
> py -3.11 -m venv PoP_venv
242+
> py -3.12 -m venv PoP_venv
243243
244244
while on Mac or Linux you would type:
245245

246246
.. code-block:: console
247247
248-
$ python3.11 -m venv PoP_venv
248+
$ python3.12 -m venv PoP_venv
249249
250250
If you're using a different version of Python then modify the command according
251251
to the discussion in section :numref:`run_version`.

searchindex.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)