From 369b6fab25b55ceb363ba2a8cb7e0f1a88ef8f8d Mon Sep 17 00:00:00 2001 From: Anssi Kääriäinen Date: Thu, 30 May 2013 10:25:58 +0300 Subject: Fixed #18169 -- NoReverseMatch not silenced if from block.super --- docs/releases/1.6.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs') diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt index 91dda667f1..cd665a775e 100644 --- a/docs/releases/1.6.txt +++ b/docs/releases/1.6.txt @@ -616,6 +616,12 @@ Miscellaneous stored as ``null``. Previously, storing a ``blank`` value in a field which did not allow ``null`` would cause a database exception at runtime. +* If a :class:`~django.core.urlresolvers.NoReverseMatch` exception is risen + from a method when rendering a template it is not silenced. For example + {{ obj.view_href }} will cause template rendering to fail if view_href() + raises NoReverseMatch. There is no change to {% url %} tag, it causes + template rendering to fail like always when NoReverseMatch is risen. + Features deprecated in 1.6 ========================== -- cgit v1.3