You can view the actual workshop material live at: http://opentechschool.github.io/python-data-intro/
This is a friendly how-to for contributors to the Introduction to Data Processing with Python course at OpenTechSchool. First, a quick refresher on the course:
Have you ever found yourself doing something methodical and repetitive with a computer, and wondered why there wasn't a better way to do it? Have you ever had some data, maybe a text file or a set of numbers, that you'd like to know some simple things about?
You will only need a laptop and a very basic understanding of Python. If you've done our Introduction to Programming workshop then this will be perfect.
This course is aimed at following on directly from the Introduction to Programming. This means it only covers the basics of reading, writing and processing text files with Python. Programmers looking to become "Data Scientists" will need to wait for a later course. :)
At OpenTechSchool we tend to go practical and at your own pace.
Practical meaning that we aren't big on theory, or requiring that people understand something completely before using it. We aren't expecting any of the students to become computer scientists. Generally programming for our students is a way of solving some practical problem. If they want to accomplish it with LISP or a spreadsheet is entirely up to them.
At your own pace means that we provide access to the complete course notes at the beginning of the session. Then students can progress individually. Some students will get through very quickly, others will take some time, and most will finish the core work with time to spare. The core work should be completable by everyone. To keep things interesting we supply various additional topics which are entirely optional.
A class schedule looks like this:
1200 - Students still arriving, writing name tags, setting up laptops. 1230 - Introductions, wifi instructions and location of coursework. 1235 - Students learn stuff. 1545 - Thankyous, maybe demonstrations.
As you can see, the schedule just has a big chunk of 'learn stuff'. We like to keep things open.
So, fork this repository. The guide is written as a Jekyll site, hosted on GitHub pages. It's set up so you can just write pages in Markdown. A markup guide is below.
Course work goes under
extras/. It's all linked together by
index.md in the root directory.
core/covers the basic goals of the course. Put any images in
extras/are all the interesting things people can do once they have completed the basics.
It's easiest to start at the end. Think of a fun and interesting topic to add to the extras. Then you can copy this file to get an idea for formatting.
When you push to github, the official site at http://opentechschool.github.io/python-data-intro gets automatically updated.
To generate and view the site (with correct CSS, etc.) with your on your local computer, you can install Jekyll and then run it like this:
If you have docker installed on your system the easiest way to test the site locally is by running
It will download a suitable docker image for jekyll and run the code within this container, making it available via http://localhost:4000/python-data-intro/
Alternatively, you can run the following steps manually:
jekyll --serve --auto # or jekyll serve --watch
Then browse to http://localhost:4000/python-data-intro/index.html to view the generated workshop content. If you leave the server running then Jekyll will automatically regenerate the site when it changes.
- We use long-lines (no newlines in paragraphs) to keep diffs moderately sane.
- Code is indented with 4 spaces.
- HTML/CSS is indented with 2 spaces.
I use Emacs 24, with markdown-mode (Ubuntu emacs-goodies-el) and gfm-mode (GitHub markdown minor-mode). Set
longlines-show-hard-newlines if you want to see where all the newlines are. These settings are useful:
(add-to-list 'auto-mode-alist '("\\.md\\'" . markdown-mode)) (setq-default indent-tabs-mode nil)
In Vim, you might like these settings:
set tabstop=4 set shiftwidth=4 set expandtab
First level section
Second level section
Third level section
Fourth level section
- List item
- Sub item
- Sub item 2
- List it m 2
- Ordered list item
- Ordered list item 2
- Ordered list item 3
- Sub item 1
- Sub item 2
- Ordered list item 4
- Ordered sub item 1
- Ordered sub item 2
- Ordered list item 5
emphasis text for emphasis
strong text for strong
Getting literal with
Or use an indent of 4 spaces, to get yourself a code block, that looks lovely.
Do a bit of blockquoting. You can still reflow the text as much as you like. Newlines are awesome. And made of win.
This is a horizonal rule:
If you want to highlight some ruby code:
def foo puts 'foo' end
Bit of command line:
$ holla holla get dolla $
Custom syntax highlighting for jupyter-notebook style code blocks is possible using an html tag in your markdown:
<div class="jupyter"> ```python print('test') ``` test </div>
The code format can be generated from jupyter by clicking the download-as -> markdown button. Each block of input and output has to be enclosed in a separate div tag.
For a more complete list of languages see highlight.js