Make RequestContext act as a dictionary

[Marc Garcia]

When creating the context, using RequestContext to include context processors content, the next doesn't work:

 context = dict(example=value)
 context.update(RequestContext(request))

instead I can use

 context = requestContext(request)
 context.update(dict(example=value))

but I think that also allowing the first case would avoid some confusion.

[Matthias Kestenholz]

This ticket makes not much sense to me. The Context is more than a simple dict, it is a stack container offering functions which cannot be easily emulated using a dict.

Although it would be possible to further emulate a dict I think this would send a wrong message to the user. Why would you want to construct a RequestContext, update a dict with it and then again create a Context to render the template?

[Eric Holscher]

I ran into this as well, but don't know if it's a "good thing"

[Julien Phalip]

This is a valid point. The context is generally assumed to be a dictionary, so RequestContext should behave as such.

[Julien Phalip]

Ok, after a second thought, there's an easy way around this:

from django.template import Context
context = Context(dict(example=value))
context.update(RequestContext(request))

[(none)]

Milestone post-1.0 deleted

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Florian Apolloner]

I don't see much gain in it -- especially since one usually passes RequestContext as context_instance and not via the normal dict.