Django 1.8.5 release notes¶
October 3, 2015
Django 1.8.5 fixes several bugs in 1.8.4.
Correction de bogues¶
- Made the development server’s autoreload more robust (#24704).
- Fixed
AssertionErrorin some delete queries with a model containing a field that is both a foreign and primary key (#24951). - Fixed
AssertionErrorin some complex queries (#24525). - Fixed a migrations crash with
GenericForeignKey(#25040). - Made
translation.override()clear the overridden language when a translation isn’t initially active (#25295). - Fixed crash when using a value in
ModelAdmin.list_displaythat clashed with a reverse field on the model (#25299). - Fixed autocompletion for options of non-
argparsemanagement commands (#25372). - Alphabetized ordering of imports in
from django.db import migrations, modelsstatement in newly created migrations (#25384). - Fixed migrations crash on MySQL when adding a text or a blob field with an unhashable default (#25393).
- Changed
Countqueries to executeCOUNT(*)instead ofCOUNT('*')as versions of Django before 1.8 did (#25377). This may fix a performance regression on some databases. - Fixed custom queryset chaining with
values()andvalues_list()(#20625). - Moved the unsaved model instance assignment data loss check on reverse relations to
Model.save()(#25160). - Readded inline foreign keys to form instances when validating model formsets (#25431).
- Allowed using ORM write methods after disabling autocommit with
set_autocommit(False)(#24921). - Fixed the
manage.py test --keepdboption on Oracle (#25421). - Fixed incorrect queries with multiple many-to-many fields on a model with the
same ‘to’ model and with
related_nameset to ‘+’ (#24505, #25486). - Fixed pickling a
SimpleLazyObjectwrapping a model (#25389).