From e77462249339f465395f49f0d0b149b670a696f3 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 24 Nov 2014 07:31:05 -0500 Subject: [PATCH] Moved release note for refs #21281 from "deprecation" to "backwards incompatible". --- docs/releases/1.8.txt | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt index d5e66480bb..911d3d63a3 100644 --- a/docs/releases/1.8.txt +++ b/docs/releases/1.8.txt @@ -698,6 +698,14 @@ in the view. If you were relying on the fact context data in a ``TemplateResponse`` could be overridden using a context processor, you will need to change your code. +Overriding ``setUpClass`` / ``tearDownClass`` in test cases +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The decorators :func:`~django.test.override_settings` and +:func:`~django.test.modify_settings` now act at the class level when used as +class decorators. As a consequence, when overriding ``setUpClass()`` or +``tearDownClass()``, the ``super`` implementation should always be called. + Miscellaneous ~~~~~~~~~~~~~ @@ -1047,14 +1055,6 @@ to construct the "view on site" URL. This URL is now accessible using the sure to provide a default value for the ``form_class`` argument since it's now optional. -Overriding ``setUpClass`` / ``tearDownClass`` in test cases -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The decorators :func:`~django.test.override_settings` and -:func:`~django.test.modify_settings` now act at the class level when used as -class decorators. As a consequence, when overriding ``setUpClass()`` or -``tearDownClass()``, the ``super`` implementation should always be called. - ``dirs`` argument of template-finding functions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~