#14343: NoReverseMatch error message is unclear, view does exist
--------------------------------------+------------------------------------
Reporter: vdboor | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Core (URLs) | Version: 1.2
Severity: Normal | Resolution: fixed
Keywords: url, resolver | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by bpeschier):
* status: new => closed
* resolution: => fixed
Comment:
I am going to close this on the basis that the `NoReverseMatch` now
contains the tried pattern(s):
{{{
django.core.urlresolvers.NoReverseMatch: Reverse for 'webgtd-contexts-
index' with arguments '()' and keyword arguments '{}' not found. 1
pattern(s) tried: ['contexts/(?P<id>\\d*)$']
}}}
This means the `NoReverseMatch` is no longer a complete dead end: it now
provides a bit of information where to look. Since there are a lot of
reasons the pattern could not match (especially now we support
lookarounds), it is going to be very difficult to provide more
information.
--
Ticket URL: <https://code.djangoproject.com/ticket/14343#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.a69b5a98282856615a4c9b6624a82464%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
