django/docs/releases/1.8.5.txt

==========================
Django 1.8.5 release notes
==========================

*Under development*

Django 1.8.5 fixes several bugs in 1.8.4.

Bugfixes
========

* Made the development server's autoreload more robust (:ticket:`24704`).

* Fixed ``AssertionError`` in some delete queries with a model containing a
  field that is both a foreign and primary key (:ticket:`24951`).

* Fixed ``AssertionError`` in some complex queries (:ticket:`24525`).

* Fixed a migrations crash with ``GenericForeignKey`` (:ticket:`25040`).

* Made ``translation.override()`` clear the overridden language when a
  translation isn't initially active (:ticket:`25295`).

* Fixed crash when using a value in ``ModelAdmin.list_display`` that clashed
  with a reverse field on the model (:ticket:`25299`).
Added stub release notes for 1.8.5. 2015-08-19 01:52:45 +02:00			`==========================`
			`Django 1.8.5 release notes`
			`==========================`

			`Under development`

			`Django 1.8.5 fixes several bugs in 1.8.4.`

			`Bugfixes`
			`========`

Fixed #24704 -- Made the autoreloader survive SyntaxErrors. With this change, it's expected to survive anything except errors that make it impossible to import the settings. It's too complex to fallback to a sensible behavior with a broken settings module. Harcoding things about runserver in ManagementUtility.execute is atrocious but it's the only way out of the chicken'n'egg problem: the current implementation of the autoreloader primarily watches imported Python modules -- and then a few other things that were bolted on top of this design -- but we want it to kick in even if the project contains import-time errors and django.setup() fails. At some point we should throw away this code and replace it by an off-the-shelf autoreloader that watches the working directory and re-runs `django-admin runserver` whenever something changes. 2015-08-05 11:07:36 +02:00			* Made the development server's autoreload more robust (:ticket:`24704`).

Fixed #24951 -- Fixed AssertionError in delete queries involving a foreign/primary key. Thanks Anssi Kääriäinen for help. 2015-08-05 21:52:11 +02:00			* Fixed ``AssertionError`` in some delete queries with a model containing a
			field that is both a foreign and primary key (:ticket:`24951`).
Forwardported release note for refs #25040. 2015-08-22 14:50:49 +02:00
Fixed #24525 -- Fixed AssertionError in some complex queries. Thanks Anssi Kääriäinen for providing the solution. 2015-08-20 18:46:14 +02:00			* Fixed ``AssertionError`` in some complex queries (:ticket:`24525`).

Forwardported release note for refs #25040. 2015-08-22 14:50:49 +02:00			* Fixed a migrations crash with ``GenericForeignKey`` (:ticket:`25040`).
Fixed #25299 -- Fixed crash with ModelAdmin.list_display value that clashes with a model reverse accessor. 2015-08-24 17:52:58 +02:00
Fixed #25295 -- Restored 'no active translation' after language override Thanks David Nelson Adamec for the report and Tim Graham for the review. 2015-08-21 14:09:29 +02:00			* Made ``translation.override()`` clear the overridden language when a
			translation isn't initially active (:ticket:`25295`).
Fixed #25299 -- Fixed crash with ModelAdmin.list_display value that clashes with a model reverse accessor. 2015-08-24 17:52:58 +02:00
			* Fixed crash when using a value in ``ModelAdmin.list_display`` that clashed
			with a reverse field on the model (:ticket:`25299`).