#5904: reverse should be more lenient on non-existent views in the urlconf
---------------------------+------------------------------------------------
Reporter: SmileyChris | Owner: nobody
Status: closed | Component: Core framework
Version: SVN | Resolution: wontfix
Keywords: | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
Firstly, not ready for checkin, since it doesn't include a test (which
would have been one line long).
More importantly, this is covering up bugs in peoples' code. If you are
referencing a view that doesn't exist, it's equivalent to having invalid
syntax in your Python source. We shouldn't be continuing on in that case,
regardless of whether the bug is nearby or just in a referenced file.
Raising an exception is the right thing to do.
If somebody wants to make improvements in this area, come up with a way to
report such errors back to the developer when the `{% url %}` tag is used
(not via the template). Don't pretend the bug in their code doesn't exist.
--
Ticket URL: <http://code.djangoproject.com/ticket/5904#comment:2>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
