boto==2.11.0
django-storages==1.1.8
Django==1.6
South==0.8.4
Pillow==2.3.1
argparse==1.2.1
gunicorn==0.17.2
psycopg2==2.4.6
django-hstore==1.2.2
wsgiref==0.1.2
pep8==1.4.6
flake8==2.0
python-omgeo==1.5
git+https://github.com/azavea/django-registration.git
modgrammar-py2==0.9.1
django-celery-with-redis==3.0
# libsass==0.2.4
# We need libsass version 3.0, which fixes libsass issue #54
git+https://github.com/dahlia/libsass-python.git@4aa8fd3c2cef8c1
# Django comments are no longer bundled with django in
# 1.6 so we include them here
django-contrib-comments==1.5
django-threadedcomments==0.9.0
django-apptemplates==0.0.1
django-queryset-csv>=0.2.9

boto==2.11.0
django-storages==1.1.8
Django==1.6
South==0.7.6
Pillow==2.3.1
argparse==1.2.1
gunicorn==0.17.2
psycopg2==2.4.6
django-hstore==1.2.2
wsgiref==0.1.2
pep8==1.4.6
flake8==2.0
python-omgeo==1.5
git+https://github.com/azavea/django-registration.git
modgrammar-py2==0.9.1
django-celery-with-redis==3.0
# libsass==0.2.4
# We need libsass version 3.0, which fixes libsass issue #54
git+https://github.com/dahlia/libsass-python.git@4aa8fd3c2cef8c1
# Django comments are no longer bundled with django in
# 1.6 so we include them here
django-contrib-comments==1.5
django-threadedcomments==0.9.0
django-apptemplates==0.0.1
django-queryset-csv>=0.2.9

Downgrade South back to 0.7.6
Downgrade South back to 0.7.6

I originally upgraded South to version 0.8.4 because a weird error was
surfacing while I was writing new migrations. I was getting crashes with
the message "AttributeError: 'DateTimeField' object has no attribute
'model'" while adding `DateField` fields to a model. I found a
stackoverflow post (linked below) that mentions this error. There was no
accepted fix other than to upgrade South to 0.8.4. So I did, and this
error went away.

In another context that I believed to be unrelated, the upgrade to South
0.8.4 began causing a crash in a `treemap` migration on a freshly
formatted database: "django.db.utils.ProgrammingError: column
"mapfeature_ptr_id" is in a primary key". This error also turned up on
our continuous integration server once changes were merged into
master. It was eventually discovered that this was caused by the upgrade
of South.

By the grace of the spirit inside the computer, the original error that
prompted this upgrade is no longer replicable. It must have disappeared
while refactoring/squashing migrations.

So, to fix the second, crucial error, downgrade south back to 0.7.6.
