Re: Logging in Django

2010/6/21 Ian Lewis : > On Sun, Jun 20, 2010 at 12:19 PM, Russell Keith-Magee > wrote: >> On Sun, Jun 20, 2010 at 4:59 AM, David North >> wrote: >>> On 28/05/2010 16:48, Russell Keith-Magee wrote: >>> * They have

Re: Logging in Django

metaclass is works in order to understand what is being > logged). Direct logging is simpler and would work for most use cases. The aspect oriented approach would be useful as a separate library or module separate from Django IMHO. I've used Zain's jogging for a while as a nice way of using python's

Re: Logging in Django

On Sun, Jun 20, 2010 at 4:59 AM, David North wrote: > On 28/05/2010 16:48, Russell Keith-Magee wrote: >> >> The second commit will be the addition of actual logging. The >> intention here is to be initially conservative; two immediate targets >> would be to

Re: Logging in Django

On 28/05/2010 16:48, Russell Keith-Magee wrote: The second commit will be the addition of actual logging. The intention here is to be initially conservative; two immediate targets would be to replace calls to mail_admins() with logging calls, and replacing debug messages in management commands

Re: Logging in Django

On Jun 1, 2:15 pm, Russell Keith-Magee wrote: > IMHO, that use case would be better handled with two different > settings files -- one with DEBUG=True and debug logging, and one with > DEBUG=False and production logging. Having multiple settings files > isn't an unusual

Re: Logging in Django

On Jun 1, 3:07 am, Russell Keith-Magee wrote: > > My concern here is YAGNI. Can you suggest a specific use case where > this will actually be required? > I agree with the YAGNI principle generally, but to my mind it's something to bear in mind if one were implementing a

Re: Logging in Django

On Sat, May 29, 2010 at 12:46 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > > On May 28, 4:48 pm, Russell Keith-Magee <freakboy3...@gmail.com> > wrote: >> Following some discussion at the DjangoCon.eu sprints, here's what >> we've got on the table regarding

Re: Logging in Django

I added a AdminEmailHandler to my branch and pulled the upstream changes. http://github.com/kevin/django-experimental/ It now behaves very close to how django-trunk does on exception ... by default there is a streamhandler pushing to stderr and the admin email handler pushing emails to admins.

Re: Logging in Django

Well, that was just to demonstrate the point that you can have a really simple minimalist configuration if that's what you want... not that it's preferable or recommended or anything.. just that if you need/want simplicity in configuration it's there. Also, it won't end up in log/messages if

Re: Logging in Django

On May 29, 1:05 am, Waylan Limberg wrote: > > Vinay has already stated that he is making his code (which is part of > python 2.7) available to be distributed with Django so it will work on > any version that Django works on. > Yes, I've develloped my Launchpad branch (which has

Re: Logging in Django

On May 28, 10:27 pm, Kevin howerton wrote: > Indeed, though that config does exactly that with apache ... the > streamhandler by default spits everything out to stderr which is in > turn picked up by apache's logging. True, but your logging output's then interspersed

Re: Logging in Django

on). >> >> Existing projects (like Django) can use the standalone dictconfig >> project on BitBucket to get the functionality which will be in Python >> 2.7 and 3.2, for use with earlier versions of Python. So really, >> Django is using the same mechanisms as Python for log

Re: Logging in Django

"Yes, something like that is a fairly minimal configuration, but generally I've found a file-based log to be pretty much part of every site's requirement, for anything but the smallest (toy) site." Indeed, though that config does exactly that with apache ... the streamhandler by default spits

Re: Logging in Django

o) can use the standalone dictconfig > project on BitBucket to get the functionality which will be in Python > 2.7 and 3.2, for use with earlier versions of Python. So really, > Django is using the same mechanisms as Python for logging. It's good > practice to put a shallow interface between the Djan

Re: Logging in Django

ictconfig project on BitBucket to get the functionality which will be in Python 2.7 and 3.2, for use with earlier versions of Python. So really, Django is using the same mechanisms as Python for logging. It's good practice to put a shallow interface between the Django and Python logging configuration laye

Re: Logging in Django

On May 28, 8:55 pm, Kevin howerton wrote: > I see the utility of being able to have additional ways to setup the > logging, though as it is I think the biggest issue people have with > the logging stuff is that the dictconfig is already fairly > intimidating looking.  If

Re: Logging in Django

e got on the table regarding adding logging support to Django. > > The core of Vinay's work is essentially ready to go -- the logging > configuration code is an implementation of what has been accepted as a > PEP, so there's no reason for us to use anything else. > > As for l

Re: Logging in Django

of the box. -k On May 28, 12:46 pm, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > On May 28, 4:48 pm, Russell Keith-Magee <freakboy3...@gmail.com> > wrote: > > > > > > > Following some discussion at the DjangoCon.eu sprints, here's what > > we've got

Re: Logging in Django

On May 28, 4:48 pm, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > Following some discussion at the DjangoCon.eu sprints, here's what > we've got on the table regarding adding logging support to Django. > > The core of Vinay's work is essentially ready to go -- the loggi

Re: Logging in Django

On Fri, May 28, 2010 at 5:48 PM, Russell Keith-Magee wrote: > So - comments? Suggestions? Just FTR, Russ and I have been talking about this for a few days here in Berlin, and I'm in agreement with this 100%. Jacob -- You received this message because you are subscribed