Moved release note for refs #21281 from "deprecation" to "backwards incompatible". (e7746224) · Commits · Dom Sekotill / django

docs/releases/1.8.txt

+8 −8

Original line number	Diff line number	Diff line
		@@ -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
		~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~