On 1/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I'm not sure why this throws a 500 error rather than a 404, but I'm hoping somebody can help.
Typically, the pattern is to catch ObjectDoesNotExist and either recover from it or raise Http404; ObjectDoesNotExist is there to let you have a hook for catching non-existent lookups. I wonder if maybe it would help if ObjectDoesNotExist were to become a subclass of Http404, so that an uncaught ObjectDoesNotExist exception would just become a 404... -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
