Branch: refs/heads/master
Home: https://github.com/django/django
Commit: 79558c787ebfd0fe723acb061a375b19a27f18cd
https://github.com/django/django/commit/79558c787ebfd0fe723acb061a375b19a27f18cd
Author: Grzegorz Nosek <r...@localdomain.pl>
Date: 2014-02-15 (Sat, 15 Feb 2014)
Changed paths:
M django/core/urlresolvers.py
M django/views/debug.py
M tests/urlpatterns_reverse/tests.py
M tests/view_tests/tests/test_debug.py
M tests/view_tests/views.py
Log Message:
-----------
Fixed #18373 - improved handling of Resolver404s from views
When django.core.urlresolvers.resolve was called from a view, failed
and the exception was propagated and rendered by technical_404_response,
the URL mentioned on the page was the current URL instead of the URL
passed to resolve().
Fixed by using the path attribute from the Resolver404 exception instead
of request.path_info. Also cleaned up the exceptions to use standard
named parameters instead of stuffing a dict in args[0]
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/52ff8170a72a8_7c50e7fd38139e9%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.
