As has been mentioned, they all use a RequestContext to begin with, but if you need additional custom variables to be exposed to your template, then you can pass them as a dict for the extra_context variable.
On Jul 19, 5:08 am, Chris Hoeppner <[EMAIL PROTECTED]> wrote: > Hi there! > > How does it exactly work when I want a RequestContext to be used in a > generic view. There's the context_processors key in the dict you gotta > pass it, but "A list of template-context processors to apply to the > view's template" doesn't really mean much to me, and even less after > giving it a "list" and seeing python complain about callables ;) > > Might anyone give me an example of a dict I might pass a generic view? > > Thanks guys! > > signature.asc > 1KDownload --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
