January 2, 2016
Django 1.8.8 fixes several bugs in 1.8.7.
Python 3.2 users, please be advised that we've decided to drop support for Python 3.2 in Django 1.8.x at the end of 2016. We won't break things intentionally after that, but we won't test subsequent releases against Python 3.2 either. Upstream support for Python 3.2 ends February 2016 so we don't find much value in providing security updates for a version of Python that could be insecure. To read more about the decision and to let us know if this will be problematic for you, please read the django-developers thread.
unique_togetherfield name generation by
__lenquery lookup on
ArrayFieldfor empty arrays (#25772).
datetemplate filter (#25812).
SeparateDatabaseAndStateoperation backwards (#25896).
TextFieldrespectively when using
AlterFieldon PostgreSQL (#25412).
django.views.decorators.cache.never_cache()now sends more persuasive headers (added
no-cache, no-store, must-revalidateto
Cache-Control) to better prevent caching (#13008). This fixes a problem where a page refresh in Firefox cleared the selected entries in the admin's
filter_verticalwidgets, which could result in inadvertent data loss if a user didn't notice that and then submitted the form (#22955).
loaddataskip disabling and enabling database constraints when it doesn't load any fixtures (#23372).
values()/values_list()includes a field not in the