Adrian Holovaty wrote: > On 12/21/05, Ian Holsman <[EMAIL PROTECTED]> wrote: > >>#925 - [patch] Refactor functionality of DjangoContext into >>'processors' which can be replaced or added to > > > I've added this functionality to trunk. > > Adrian > > -- > Adrian Holovaty > holovaty.com | djangoproject.com | chicagocrime.org >
Excellent. Now we just have to ask ourselves is DjangoContext vs Context going to be an obvious question for people (especially newbs) to answer. IMO its now a very weird name - "um, so this is the Django Context class, and this is the DjangoContext class..." I would vote to rename it RequestContext, or something else that makes clear what the point of it is (namely that it has special treatement for being initialised with a request). We can always keep DjangoContext as an alias. Also, I wonder if it is actually worth keeping the stuff about subclassing Context? Its not really a very workable idea, and I can't come up with a rational reason for doing it instead of writing some processors. Robert
