#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
-------------------------------------+-------------------------------------
     Reporter:  Grzegorz Nosek       |                    Owner:  Andrew
         Type:                       |  Northall
  Cleanup/optimization               |                   Status:  assigned
    Component:  Core (URLs)          |                  Version:  dev
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Natalia Bidart):

 I'm not sure if it's too late to propose to "unaccept" this ticket. I have
 read the use case, and while there is a description for a use case, that
 use case feels, to me, insufficient to make a strong argument to add this
 change of behavior in the django codebase.

 My rationale is that failing to resolve an URL in a view is, indeed,
 semantically an "url not found" (404) result. At least in my experience, I
 can think of a few reasons for a failed resolve in a view such as:

   * there is a spelling error in the url name or args (in which case the
 unit tests should caught this)
   * there is a dynamic component in the url name/params that at the time
 of the execution evaluates to something that does not exist (this still
 feels like a 404 and not a 500)
   * something else I'm missing?

 I don't think the above justify the complexity that seems to be necessary
 to solve this (following [https://github.com/django/django/pull/17007 PR
 17007]).

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22055#comment:11>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070189ad6d01d0-38372126-200e-4cdf-b07e-c737e03691cb-000000%40eu-central-1.amazonses.com.

Reply via email to