Using e.x. raise Http404 isn't clean solution. Is a very ugly shortcut. So you can return always a 404-view. All other unhandled errors given 500 - is general server error for _unhandled_ exception. Maybe I was wrong, but using exceptions is not pretty way.
Jonas Obrist schrieb: > It probably wouldn't be impossible to do it yourself and I'm well aware > of the HttpResponseForbidden, but to me it doesn't makes sense that one > error is considered an exception in django and the other ones responses. > I'd like to see a unified way to handle this in Django and not just in > my app. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
