John M wrote: > Curious, does that give you the full user context too? Yes, all generic views use RequestContext. Which means you have not only 'user' available but everything that your context processors provide. They are listed in settings as TEMPLATE_CONTEXT_PROCESSORS and you can use your own processors there and your context will also be passed to templates.
> I noticed with > render_to_response() does not 'easily' use the user context. Yes, this is because 'render_to_response' was made as a simple dumb shortcut for loading a template and rendering it with a context. May be it worth to change it to be more suitable for the most common case to accept 'request' and user RequestContext too. I think 'context_instance=RequestContext(request)' is just a little big boilerplate to use it in every view... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
