On Tue, Nov 27, 2012 at 12:38 PM, Wade Williams
wrote:
> I share the disdain for global variables as well.
>
> I'm fairly new to Django, and what I'm not understanding is when the
> request object is available for inclusion. I have a custom session backend
> that I've
Tue, Nov 27, 2012 at 2:39 AM, Mike S <mse...@gmail.com >wrote:
>
>> Sometimes it is very inconvenient to make the `request` object available
>> deep in the call stack, so I wrote a short middleware to work around this
>> issue:
>>
>> http://djangosnippets.org/sn
ometimes it is very inconvenient to make the `request` object available
> deep in the call stack, so I wrote a short middleware to work around this
> issue:
>
> http://djangosnippets.org/snippets/2853/
>
>
> On Monday, November 26, 2012 5:16:01 AM UTC-5, Miaobing Jiang wrote:
>>
Sometimes it is very inconvenient to make the `request` object available
deep in the call stack, so I wrote a short middleware to work around this
issue:
http://djangosnippets.org/snippets/2853/
On Monday, November 26, 2012 5:16:01 AM UTC-5, Miaobing Jiang wrote:
>
> how should
On Monday, 26 November 2012 10:16:01 UTC, Miaobing Jiang wrote:
> how should I get the request object when I need that object in some places
> rather than in the view for each view has request as its first parameter?
>
Pass it from the view into whatever functions need it.
--
DR.
how should I get the request object when I need that object in some places
rather than in the view for each view has request as its first parameter?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the
6 matches
Mail list logo