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 with this middleware i have it already :|
On Thu, May 24, 2012 at 4:46 PM, bruno desthuilliers < bruno.desthuilli...@gmail.com> wrote: > On May 24, 12:35 pm, Alireza Savand <alireza.sav...@gmail.com> 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 command ? > > From experience with some other frameworks / technos, (PHP, Zope / > Plone, etc), it's a pretty bad idea to depend too much on a "current > request" - it leads to way to much coupling in parts of the code that > should be able to work in any environment. Trying to do anything > commandline with Plone is just a major PITA, when not bordering on > impossible. > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
