On May 24, 2:57 pm, Alireza Savand wrote:
> On Thursday, May 24, 2012 4:46:34 PM UTC+4, bruno desthuilliers wrote:
>
>
> > Uhu... What if I'm running my code from the shell or a command ?
>
> By the way, there is also *set_request*(*request*) for that situation.
Yes. In
On Thursday, May 24, 2012 4:46:34 PM UTC+4, bruno desthuilliers wrote:
>
> On May 24, 12:35 pm, Alireza Savand wrote:
> > Hi
> > Yesterday i released an app for django.
> > *Basically it's just a middleware to access current request of your
> django
> >
So what about logging stuff.
To doing some logging at strange places that i need that request object.
specially in deeper and deeper methods/functions. i have to pass the
request object to alot of functions which i don't need it in there exaclty
but i will need it in inner method, classes.
But
On May 24, 12:35 pm, Alireza Savand wrote:
> Hi
> Yesterday i released an app for django.
> *Basically it's just a middleware to access current request of your django
> application from anywhere in your code.*
Uhu... What if I'm running my code from the shell or a
On Thursday, 24 May 2012 11:35:37 UTC+1, Alireza wrote:
>
> Hi
> Yesterday i released an app for django.
> *Basically it's just a middleware to access current request of your
> django application from anywhere in your code.*
> Other information described in the README and pypi page.
>
> pypi:
>
Hi
Yesterday i released an app for django.
*Basically it's just a middleware to access current request of your django
application from anywhere in your code.*
Other information described in the README and pypi page.
pypi:
http://pypi.python.org/pypi/django-crequest
github repo:
6 matches
Mail list logo