#5904: reverse should be more lenient on non-existent views in the urlconf
-------------------------------------+--------------------------------------
          Reporter:  SmileyChris     |         Owner:  nobody
            Status:  reopened        |     Milestone:        
         Component:  Core framework  |       Version:  SVN   
        Resolution:                  |      Keywords:        
             Stage:  Accepted        |     Has_patch:  1     
        Needs_docs:  0               |   Needs_tests:  0     
Needs_better_patch:  1               |  
-------------------------------------+--------------------------------------
Changes (by mtredinnick):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted

Comment:

 It's reasonable that the `url` tag should catch the error and do nothing
 -- that's normal template behaviour and not doing so is a bug. A patch to
 fix that would be good.

 However, the behaviour of `reverse()` with respect to the error reporting
 it does now should be unchanged. It's an '''error''' to refer to invalid
 view files. Equivalent to having syntax errors in your code or randomly
 deleting files. There's simply no way to argue otherwise. You might hope
 for less draconian error handling, but that would be disguising symptoms.
 The correct fix is to fix the bugs in the code that causes the problem (it
 takes two seconds to comment out a line that isn't implemented yet, for
 example). So no change to `reverse()` behaviour is required.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/5904#comment:4>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to