You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 0_introduction.html
+108-1Lines changed: 108 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -177,7 +177,114 @@ <h3><span class="section-number">1.1.3. </span>The quizes<a class="headerlink" h
177
177
<divclass="section" id="the-exercises">
178
178
<h3><spanclass="section-number">1.1.4. </span>The exercises<aclass="headerlink" href="#the-exercises" title="Permalink to this headline">¶</a></h3>
179
179
<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 <codeclass="xref std std-numref docutils literal notranslate"><spanclass="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
+
<divclass="section" id="getting-help">
194
+
<h3><spanclass="section-number">1.1.5. </span>Getting help<aclass="headerlink" href="#getting-help" title="Permalink to this headline">¶</a></h3>
195
+
<divclass="admonition note">
196
+
<pclass="admonition-title">Note</p>
197
+
<p>Write this bit once the interaction format is finalised.</p>
198
+
</div>
199
+
</div>
200
+
<divclass="section" id="writing-an-issue-report">
201
+
<h3><spanclass="section-number">1.1.6. </span>Writing an issue report<aclass="headerlink" href="#writing-an-issue-report" title="Permalink to this headline">¶</a></h3>
202
+
<divclass="admonition note">
203
+
<pclass="admonition-title">Note</p>
204
+
<p>Write this bit.</p>
205
+
</div>
206
+
</div>
207
+
<divclass="section" id="assessment">
208
+
<h3><spanclass="section-number">1.1.7. </span>Assessment<aclass="headerlink" href="#assessment" title="Permalink to this headline">¶</a></h3>
<h2><spanclass="section-number">1.2. </span>Obtaining the right software tools<aclass="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><olclass="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
+
<divclass="section" id="windows">
225
+
<h3><spanclass="section-number">1.2.1. </span>Windows<aclass="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 <aclass="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 <aclass="reference external" href="https://git-scm.com/download/win">official Git website</a>.</p>
231
+
<p>Visual Studio Code can be downloaded from <aclass="reference external" href="https://code.visualstudio.com">Microsoft</a>.</p>
232
+
</div>
233
+
<divclass="section" id="macos">
234
+
<h3><spanclass="section-number">1.2.2. </span>MacOS<aclass="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 <aclass="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 ⌘ + <codeclass="xref py py-obj docutils literal notranslate"><spanclass="pre">space</span></code> to open Spotlight Search,
240
+
and type <codeclass="xref py py-obj docutils literal notranslate"><spanclass="pre">terminal</span></code> followed by return. Now copy the following line and paste it
<p>Once again, you finish by pressing the return key (⏎).</p>
252
+
<p>To install Visual Studio Code, follow the instructions on the <aclass="reference external" href="https://code.visualstudio.com/docs/setup/mac">Microsoft website</a>.</p>
253
+
</div>
254
+
<divclass="section" id="linux">
255
+
<h3><spanclass="section-number">1.2.3. </span>Linux<aclass="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
0 commit comments