Skip to content

CODE1.md

Latest commit

 

History

History
165 lines (120 loc) · 5.21 KB

CODE1.md

File metadata and controls

165 lines (120 loc) · 5.21 KB


At a glance... | Syllabus | Models | Code | Lecturer

Code1: coding homework

What to Hand in

After doing all the following, you should be able to write one file hw/code/1/README.md in your repo showing:

  • A screen snap of the top level of your repo
  • Output of the commands python --version, pip help, easy_install -h
  • A screen shot of what it looks like to write code in your preferred Python IDE (hint: need to see syntax highlighting).
  • A screenshot of output of your okok.py test (defined below).

Using some URL shortener (e.g. goo.gl), shorten the URL to hw/code/1/README.md and paste into the submission page.

Instructions

Get your Git on

  • Create a public Github repository for all your work for this subject. + The name of that repo should be x9115xxx where xxx is anything you like.
  • Invite timm and rahink to that repo.
  • Add directories to that repo + project + paper + hw/read + hw/code/1 + hw/code/2 + hw/code/3 + ... + hw/code/9

Get your Python On

Make sure you can can get to Python 2.7

For this subject, the lecturer and support will support your Python code on the intenet IDE Cloud9. You can use any other platform you like, of course, but any systems issues (e.g. installing of important packages) are your responsibility.

While you do not need to use Cloud9, you do need to show that you have a power platform for Python development:

  • Check you have pip installed
  • Check you have easy_install install
  • Check your code editor does syntax highligting of your Python code.

Get your Test-Driven Development On.

  1. Watch the great Kent Beck video on how to write a test engine in just a few lines of code. Note that that example is in CoffeeScript. For the equivalent Python code, see ok.py.
  2. Get the Python equivalent of the watch command used by Beck. Specifically, run the command sudo pip install rerun
  3. Download the files
  4. Get two windows open:
    • One editting okok.py
    • One in a shell
  5. In the shell, type rerun "python -B okok.py"
  6. Add one more unittest to okok.py.
    • Important... leave behind at least one failing test.
  7. Your screen should now look something like this:

utest

Hints

Images in Markdown

To include images in your markdown...

![soemTExt](image.png)

If the image is too wide, you can also use

<img src="image.png" width=500>

Help with Git and Github

If you need tutorial help with Gitbub, see the tutor. But, for a cheats guide, here is the Makefile that the lecturer drops into all his repos:

# File:  setup/Makefile (from github.com/txt/evil)
# Usage: make
typo:   ready
    @- git status
    @- git commit -am "saving"
    @- git push origin master # insert your branch names here

commit: ready
    @- git status
    @- git commit -a
    @- git push origin master

update: ready
    @- git pull origin master

status: ready
    @- git status

ready:
    @git config --global credential.helper cache
    @git config credential.helper 'cache --timeout=3600'

timm:  # <== change to your name
    @git config --global user.name "Tim Menzies" #<== your name
    @git config --global user.email [email protected] #<== your email

Working with Cloud9

As of June 2015, the procedure for doing that was:

  • Go to Github and create an empty repository.
  • Log in to Cloud9 using your GitHub username (at http://c9.io, there is a button for that, top right).
  • Hit the green CREATE NEW WORKSPACE button
    • Select Clone from URL;
    • Find Source URL and enter in http://github.com/you/yourRepo
    • Wait ten seconds for the screen to change.
    • Hit the green START EDITING button.

This will drop you into the wonderful Cloud9 integrated development environment. Here, you can edit code and (using the above Makefile) run make typo to backed up your code outside Cloud9, over at Github.com (which means that if ever Cloud9 goes away, you will still have your code).

The good news about Cloud9 is that it is very easy to setup and configure. The bad news is that each Cloud9 workspace has the same limits as Github- a 1GB size limit. Also, for CPU-intensive applications, shared on-line resources like Cloud9 can be a little slow. That said, for the newbie, Cloud9 is a very useful tool to jump start the learning process.

For sites other than Cloud9, see Koding, Nitrous.IO and many more besides.

Copyright © 2015 Tim Menzies. This is free and unencumbered software released into the public domain.
For more details, see the license.