For the September 27th, 2012, PySIG meeting

We plan a follow along on your laptop introduction to Django, using the official tutorial at this meeting.  Of course you can just look over people's shoulders, or just at the projected presentation, but if you want to follow along on your box, please be sure to have the following:

  1. A suitable version of Python.  Django claims to run on 2.5, 2.6, or 2.7, but your presenter will be using 2.7, so for best match to the presentation, you may want to be sure you have a 2.7.x python.  (NOTE: it is relatively easy to have multiple versions of Python installed on a box, but, especially for Linux users, be sure that you are adding a 2.7, rather than replacing your box's native version, possibly used for system scripts in non-compatible ways.)
  2. Have a Python friendly editor.  From my point of view, that means that while the tab key indents, it dows so using spaces, not tab characters.  You can get away with having tabs in python files, but getting everyone's editor to agree on what they mean is a challenge., particularly if you use my repository of pre typed code (see point 5, below).
  3. Have pip installed for the 2.7 python.  That is, be sure that pip-2.7 is available.  (Just plain pip may or may not invoke the same command.  Also, if it's installed for you python2.7, you should be able to start python2.7 and say "import pip" without getting an error.  NOTE that distribute is a prerequsite for pip, so if you don't already have pip, you are probably going to have to install distribute first.  So get the files distribute_setup.py and get-pip.py and do "sudo python2.7 distribute_setup.py" and "sudo python2.7 get-pip.py".
  4. Get virtualenv.  It's not absolutely necessary, but I strongly advise it for this tutorial.  Unlike pip, this doesn't have to be installed in the 2.7 Python, since when you use it, you can tell it which python you want to be used by the virtual environment that you are creating.  So just do "sudo pip install virtualenv"  (I presume that this also works on Windows and Mac, but I can't promise.)
  5. Install Mercurial.  This is optional, but I'll be providing a repository with the various stages of the tutorial as revisions.  It will save you from typing all the boiler plates stuff suring the meeting, and will avoid searching for a lot of typos in that stuff.  (You are still free to make typos when playing with your own variations.)  Mercurial will also show you diffs between revisions.  Do "sudo pip install mercurial".  We might find someone willing to convert the repository to a git repository, for those already combortable with git.
  6. Snag this file to bring with you, though we may have some paper copies, and this web site will probably be available from the ABI.

I may add some  sub pages later with advice on installing multiple python versions, or testing that your virtualenv works, etc., so check back from time to time if you're interested in that sort of stuff.  (I guess that this didn't happen.)