Skip to content

Commit 49a52ea

Browse files
committed
Website build
1 parent 8ecb7ce commit 49a52ea

9 files changed

+808
-59
lines changed

.buildinfo

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
# Sphinx build info version 1
22
# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
3-
config: c2c1b334e2eda2af5fafd35879626589
3+
config: deaa46c820e7d7258d09a89e9a731161
44
tags: 645f666f9bcd5a90fca523b33c5a78b7

0_introduction.html

Lines changed: 108 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,114 @@ <h3><span class="section-number">1.1.3. </span>The quizes<a class="headerlink" h
177177
<div class="section" id="the-exercises">
178178
<h3><span class="section-number">1.1.4. </span>The exercises<a class="headerlink" href="#the-exercises" title="Permalink to this headline"></a></h3>
179179
<p>As we’ve already noted, really learning to program better is only achieved by
180-
writing code. The core of each week’s activities is therefore to ß</p>
180+
writing code. The core of each week’s activities is therefore to put the new
181+
concepts and programming structures you’ve learned into practice. The
182+
programming exercises are given at the end of each chapter, just before the
183+
glossary. Each time there will be a skeleton code available from GitHub
184+
Classroom (we’ll introduce that in <code class="xref std std-numref docutils literal notranslate"><span class="pre">github_classroom</span></code>) which provides
185+
the starting point. Sometimes you might be asked to complete a piece of code
186+
while on other occasions you’ll need to write a whole Python module from
187+
scratch. Each set of exercises will come with a matching set of tests. These are
188+
small programs which check whether your code produces the correct responses to a
189+
range of inputs. Tests like this provide immediate feedback and enable you to
190+
know how you are doing without having to wait for code to be submitted and
191+
marked.</p>
192+
</div>
193+
<div class="section" id="getting-help">
194+
<h3><span class="section-number">1.1.5. </span>Getting help<a class="headerlink" href="#getting-help" title="Permalink to this headline"></a></h3>
195+
<div class="admonition note">
196+
<p class="admonition-title">Note</p>
197+
<p>Write this bit once the interaction format is finalised.</p>
198+
</div>
199+
</div>
200+
<div class="section" id="writing-an-issue-report">
201+
<h3><span class="section-number">1.1.6. </span>Writing an issue report<a class="headerlink" href="#writing-an-issue-report" title="Permalink to this headline"></a></h3>
202+
<div class="admonition note">
203+
<p class="admonition-title">Note</p>
204+
<p>Write this bit.</p>
205+
</div>
206+
</div>
207+
<div class="section" id="assessment">
208+
<h3><span class="section-number">1.1.7. </span>Assessment<a class="headerlink" href="#assessment" title="Permalink to this headline"></a></h3>
209+
</div>
210+
</div>
211+
<div class="section" id="obtaining-the-right-software-tools">
212+
<h2><span class="section-number">1.2. </span>Obtaining the right software tools<a class="headerlink" href="#obtaining-the-right-software-tools" title="Permalink to this headline"></a></h2>
213+
<p>In order to do this module, you’ll need some core software tools. As the module
214+
proceeds we’ll also install several more Python packages, but you don’t need to
215+
install those right now. The core tools you will need are:</p>
216+
<blockquote>
217+
<div><ol class="arabic simple">
218+
<li><p>Python version 3.6 or later.</p></li>
219+
<li><p>Git (the revision control system we’re going to use).</p></li>
220+
<li><p>A Python-aware text editor. Visual Studio Code is recommended, and all
221+
the instructions in this course will assume that this is what you are using.</p></li>
222+
</ol>
223+
</div></blockquote>
224+
<div class="section" id="windows">
225+
<h3><span class="section-number">1.2.1. </span>Windows<a class="headerlink" href="#windows" title="Permalink to this headline"></a></h3>
226+
<p>If you already have Python (3.6 or later) installed, for example because you
227+
have installed Anaconda then this is likely to be fine. Otherwise, Python for
228+
Windows can be obtained from the <a class="reference external" href="https://www.python.org/downloads/">official Python website</a>. Simply click on the download button and
229+
follow the instructions.</p>
230+
<p>Git for Windows can be downloaded from the <a class="reference external" href="https://git-scm.com/download/win">official Git website</a>.</p>
231+
<p>Visual Studio Code can be downloaded from <a class="reference external" href="https://code.visualstudio.com">Microsoft</a>.</p>
232+
</div>
233+
<div class="section" id="macos">
234+
<h3><span class="section-number">1.2.2. </span>MacOS<a class="headerlink" href="#macos" title="Permalink to this headline"></a></h3>
235+
<p>MacOS comes with Python3, but unfortunately it’s a broken version. Usually the
236+
best option is to install the package manager <a class="reference external" href="https://brew.sh">Homebrew</a> and
237+
use that to install Python (and Git). In order to do this, you’ll need to open a
238+
terminal. This is a program which comes with MacOS and enables you to run other
239+
programs by typing text commands. Press ⌘ + <code class="xref py py-obj docutils literal notranslate"><span class="pre">space</span></code> to open Spotlight Search,
240+
and type <code class="xref py py-obj docutils literal notranslate"><span class="pre">terminal</span></code> followed by return. Now copy the following line and paste it
241+
into the terminal:</p>
242+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">/bin/bash -c &quot;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)&quot;</span>
243+
</pre></div>
244+
</div>
245+
<p>and press the return key (⏎). Enter your Mac user password when asked and
246+
Homebrew will install. Next install Python 3 and git by typing the following in
247+
the terminal window:</p>
248+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">brew install python git</span>
249+
</pre></div>
250+
</div>
251+
<p>Once again, you finish by pressing the return key (⏎).</p>
252+
<p>To install Visual Studio Code, follow the instructions on the <a class="reference external" href="https://code.visualstudio.com/docs/setup/mac">Microsoft website</a>.</p>
253+
</div>
254+
<div class="section" id="linux">
255+
<h3><span class="section-number">1.2.3. </span>Linux<a class="headerlink" href="#linux" title="Permalink to this headline"></a></h3>
256+
<p>If you are running a fairly recent version of Linux then you almost certainly
257+
have a suitable Python installed already, and may also have git installed. Open
258+
a terminal (the way you do this depends a little on distribution, but if you’re
259+
a Linux user we’ll assume you know how to do this). At the terminal prompt run
260+
this command:</p>
261+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">python --version</span>
262+
</pre></div>
263+
</div>
264+
<p>so long as it shows at least version 3.6 you should be fine. If an earlier
265+
version is shown then you’ll need to either update your distribution, or search
266+
online for how to install a more recent Python. The method will vary from
267+
distribution to distribution so we can’t provide a general solution.</p>
268+
<p>Next, type the following command in the terminal:</p>
269+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">git --version</span>
270+
</pre></div>
271+
</div>
272+
<p>So long as this actually returns a version number everything is probably fine
273+
(we don’t need a particularly new git). If you get an error that git is not
274+
found then you’ll need to install it using the package manager for your
275+
distribution. For example, if you are running Ubuntu or another Debian-based
276+
distribution, the command would be:</p>
277+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">sudo apt-get install git</span>
278+
</pre></div>
279+
</div>
280+
<p>while on RedHat-distributions such as Fedora or CentOS, the command would be:</p>
281+
<div class="highlight-console notranslate"><div class="highlight"><pre><span></span><span class="go">sudo dnf install git-all</span>
282+
</pre></div>
283+
</div>
284+
<p>On other distributions the command will be different. The simplest option is to
285+
search online for how to install git on your distribution.</p>
286+
<p>In order to install Visual Studio code you simply follow the instructions on the
287+
<a class="reference external" href="https://code.visualstudio.com/download">Microsoft website</a>.</p>
181288
</div>
182289
</div>
183290
</div>

0 commit comments

Comments
 (0)