On Oct 2, 1:59 am, Kevin Howerton <kevin.hower...@gmail.com> wrote: > Also didn't realize that adding a nullhandler to just the root logger > would remove those warnings (pretty cool)... ended up writing a bit > that adds a nullhandler to any logger without handlers for my > implementation in lumberjack... woops. >
Yes, that's because a search is done for handlers in all ancestors of a logger (except when propagate is sent to False - ancestor scanning stops there). A very common case is for an application developer to just add handlers to the root logger, to capture events from all components/ libraries used. That's usually what you need for development, though sometimes you also have files fed by just one component (e.g. SQL queries) . For production, of course, you have e.g. email handlers for critical stuff as well, plus files just to catch errors, and so on. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
