tickets: 8177
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8177 | 2008-08-09 01:31:38 | 2011-09-28 16:12:17 | 2022-03-06 03:41:33.946180 | Accepted | closed | Core (Other) | dev | fixed | reverse() should report the reverse lookup that fails. | Now that {% url foo %} does not fail silently any more, it's really important to report which reverse lookup failed. Compare: {{{ Before the attached patch: -------------------------- Django version 1.0-alpha_2-SVN-8255, using settings 'trunk.settings' Development server is running at http://127.0.0.1:8000/ Quit the server with CONTROL-C. Traceback (most recent call last): ... File "/usr/lib/python2.5/site-packages/django/core/urlresolvers.py", line 291, in reverse raise NoReverseMatch NoReverseMatch After the attached patch: -------------------------- Django version 1.0-alpha_2-SVN-8255, using settings 'trunk.settings' Development server is running at http://127.0.0.1:8000/ Quit the server with CONTROL-C. Traceback (most recent call last): ... File "/usr/lib/python2.5/site-packages/django/core/urlresolvers.py", line 291, in reverse raise NoReverseMatch("Reverse for '%s' not found." % lookup_view) NoReverseMatch: Reverse for 'foo-bar' not found. }}} Run a `rgrep foo-bar .` and you find the offending place easily. | nobody | mrts | reverse | 0 | 1 | 0 | 0 | 0 | 0 |