Re: class based views: object instead of dictionary as context?

Hi Reinout, IMHO, Django's philosophy is that template designers are highly skilled designers and not coders. To make it possible for designers to edit the templates themselves, Django requires the developer to create a simple context dictionary for designers to understand. In all of my

class based views: object instead of dictionary as context?

Hi, I've got one big what's-the-design-decision/reason question regarding django 1.3's new class based views: why does django encourage a hand-crafted context dictionary instead of "just" passing the view object along? In zope/plone, I was used to having the view object available in the

Exceptions thrown from middleware

Hi all Currently, if a view throws an exception, the middleware classes that have a process_exception method will be called in reverse order to see if one of them can handle it and return a valid response before django's default exception handling takes over. This doesn't hold true for