Quote all {% url %} arguments, as required by Django 1.5+.

This removes support for Django 1.2, which requires unquoted view names.
Update settings as no longer supporting Django 1.2.
Increase Country.code maximum length to 3.

Fixes #85.
Increase Area.name maximum length to 2000, to match Name.
Increase Type.code maximum length to 500 characters.

It might as well be consistent with Code.code. Fixes #86.
Post deploy script.

Sets up virtualenv, installs packages, compiles CSS, updates the
database, and gathers the static files.
Drop support for Django 1.3.

Move to Django 1.4+ file layout, remove any old-Django workarounds,
tidy up settings.
Allow a couple more characters in callback.
Check if the returned name is already Unicode.

Django 1.5 (specifically 9a2bceed) changes the behaviour of DataSource
feature lookup, returning a unicode string rather than the str it did
previously. So check whether we've been given a unicode string before
trying to convert it.
Fix and improve broken install script.

It wouldn't work at all, because it wasn't using a virtualenv and e.g.
on Ubuntu precise you'll only get Django 1.3 that way. Now, use the
separate post deploy script that now exists, and run gunicorn using the
virtualenv's python. Don't install compass, it isn't needed; update the
example config files; add more output.
Travis working somewhat; it's using PostGIS 2.1.

Travis already has PostGIS installed. This means Django 1.4 will fail,
it only got proper support for PostGIS 2 with 1.5.
Include legacy_gist.sql to support Django 1.4/PostGIS 2.
Kill correct processes.
The admin requires the messages framework, whoops.
Use local copy of Django pony.
Use static template tag for static assets.
Add needed <Document> element to KML output.
Version 1.0.2.
Limit area lookups by unit_id to the current generation.

There can be areas from previous generations which share the same unit_id but which are different. EG: http://mapit.mysociety.org/area/143398.html replaced http://mapit.mysociety.org/area/15941.html but kept the same unit_id. Without this additional lookup we don't know which one to check
Add control file for October 2013 boundary line changes.

Some manual workarounds needed for boundaries which have got new GSS codes but we don't want new areas to be created for them.