Perfect!
I read about the context processors before and that's why I originally
opted to use RequestContext (if only for the 'user' variable being
accessible everytime). Adding my own context processor for this
particular case hadn't cross my mind. Everything now works exactly as
I would like it
Perfect!
I read about the context processors before and that's why I originally
opted to use RequestContext (if only for the 'user' variable being
accessible everytime). Adding my own context processor for this
particular case hadn't cross my mind. Everything now works exactly as
I would like it
Perfect!
I read about the context processors before and that's why I originally
opted to use RequestContext (if only for the 'user' variable being
accessible everytime). Adding my own context processor for this
particular case hadn't cross my mind. Everything now works exactly as
I would like it
On Jun 9, 5:23 am, EricR86 wrote:
> Hello,
>
> I have a small issue in terms callable objects inside of contexts. I'm
> having trouble figuring out how to have the call evaluated everytime
> the context is used/rendered. An example:
>
> some_context = {
> 'random': random(),
>
> }
>
> def som
Hello,
I have a small issue in terms callable objects inside of contexts. I'm
having trouble figuring out how to have the call evaluated everytime
the context is used/rendered. An example:
some_context = {
'random': random(),
}
def some_view(request):
return render_to_response('some_tem
5 matches
Mail list logo
