Jacob Kaplan-Moss wrote:
Thanks for the heads up; I've fixed the error in [1909].
On a similar note... Right after template context processors there is a mention of the ability to subclass the standard context and there are two warnings about remembering to use it and not overriding default variables.
I think that more severe disadvantage of subclassing is that one can't use generic views with a custom context (unless I'm missing something). And this should be mentioned explicitely.
Also I would add that subclassing is ever needed only when one wants to do something extremely fancy with the standard context, fields addition is solved entirely by processors. Otherwise we have two ways of doing this thing that look very similar from the documentation.
And also based on principle of doing things only one way I'd rather dropped the third parameter with a list of processors from DjangoContext. Why the list in the settings is not enough?
