Re: [Django] #14343: NoReverseMatch error message is unclear, view does exist

[Django]

#14343: NoReverseMatch error message is unclear, view does exist
--------------------------------------+------------------------------------
Reporter: vdboor | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (URLs) | Version: 1.2
Severity: Normal | Resolution:
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
--------------------------------------+------------------------------------

Comment (by aaugustin):

#19091 was a duplicate.

--
Ticket URL: <https://code.djangoproject.com/ticket/14343#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#14343: NoReverseMatch error message is unclear, view does exist
--------------------------------------+------------------------------------
Reporter: vdboor | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (URLs) | Version: 1.2
Severity: Normal | Resolution:
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
--------------------------------------+------------------------------------

Comment (by aaugustin):

#18373 is related.

--
Ticket URL: <https://code.djangoproject.com/ticket/14343#comment:8>

[Django]

#14343: NoReverseMatch error message is unclear, view does exist
--------------------------------------+------------------------------------
Reporter: vdboor | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (URLs) | Version: 1.2
Severity: Normal | Resolution:
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
--------------------------------------+------------------------------------

Comment (by Wilfred):

#17076 is related.

--
Ticket URL: <https://code.djangoproject.com/ticket/14343#comment:9>

[Django]

#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>