--
Ticket URL: <https://code.djangoproject.com/ticket/32998>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => needsinfo
* component: Uncategorized => HTTP handling
Comment:
It works for me. Please reopen the ticket if you can debug your issue and
provide more details or a sample project. If you're having trouble
understanding how Django works, see
TicketClosingReasons/UseSupportChannels for ways to get help.
--
Ticket URL: <https://code.djangoproject.com/ticket/32998#comment:1>
* Attachment "process_view-error.zip" added.
* status: closed => new
* resolution: needsinfo =>
Comment:
See the attachment.
--
Ticket URL: <https://code.djangoproject.com/ticket/32998#comment:2>
* status: new => closed
* resolution: => invalid
Comment:
process_view() is run after the URL is resolved. (That's how the view
`callback` parameter is populated.) So, if resolution raises a 404,
process_view() will not be called. This is expected AFAICS.
--
Ticket URL: <https://code.djangoproject.com/ticket/32998#comment:3>
Comment (by jooadam):
Replying to [comment:3 Carlton Gibson]:
> process_view() is run after the URL is resolved. (That's how the view
`callback` parameter is populated.) So, if resolution raises a 404,
process_view() will not be called. This is expected AFAICS.
I would definitely not expect this, or for that matter, to reference the
other issue I opened, that errors in a 404 not get logged. Django calls
error handlers views, so I would expect them to work the same way as
ordinary views, or call them something else. Or the very least, document
that they are exceptional.
--
Ticket URL: <https://code.djangoproject.com/ticket/32998#comment:4>