On 7/24/06, Simon Willison <[EMAIL PROTECTED]> wrote: > It would be nice if we could catch this and provide a friendly error > message, maybe by having an assertion somewhere that checks that the > view function has returned an object that is an instance (or > subclass) of HttpResponse.
That'd probably be a good idea; I remember being somewhat befuddled when I wrote up my "how Django processes a request" at not being able to find anything that checked whether the return value from the view (or middleware, if that's what ends up returning) was an HttpResponse. At the time I chalked it up to sleep deprivation and lack of intimate familiarity with the relevant code. -- "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 -~----------~----~----~----~------~----~------~--~---
