Comments on: Reusable Logging in Django Apps http://mihasya.com/blog/reusable-logging-in-django-apps/ good things now come in packages of three Sat, 23 Jul 2011 22:40:16 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: mihasya http://mihasya.com/blog/reusable-logging-in-django-apps/comment-page-1/#comment-141 mihasya Tue, 03 Mar 2009 07:54:00 +0000 http://mihasya.com/blog/?p=237#comment-141 <p>The reason for storing it in the settings.py file is that you can then import from django.conf.settings, which is universal - you can move your app into another project and just define a LOGGER in that project's settings.py. That is also the reason for the silent swap for the generic logger - if you have a LOGGER or generic logging configured, it'll just work. If you haven't configured logging at all, the log output will just go to stdout, so it's not entirely silent. It's not optimal, but my goal was to create a way for apps to be able to use a project-wide logger w/o making too big a fuss about it. If you really NEED the logs and have them configured, you will very quickly notice that the output isn't coming, and will then have an easy way to fix it.</p> The reason for storing it in the settings.py file is that you can then import from django.conf.settings, which is universal – you can move your app into another project and just define a LOGGER in that project’s settings.py. That is also the reason for the silent swap for the generic logger – if you have a LOGGER or generic logging configured, it’ll just work. If you haven’t configured logging at all, the log output will just go to stdout, so it’s not entirely silent. It’s not optimal, but my goal was to create a way for apps to be able to use a project-wide logger w/o making too big a fuss about it. If you really NEED the logs and have them configured, you will very quickly notice that the output isn’t coming, and will then have an easy way to fix it.

]]> By: Amit Upadhyay http://mihasya.com/blog/reusable-logging-in-django-apps/comment-page-1/#comment-140 Amit Upadhyay Tue, 03 Mar 2009 05:11:19 +0000 http://mihasya.com/blog/?p=237#comment-140 <p>Nice tip.</p> <p>I tend to store all my logging related settings to loggers.py and loggers.cfg in the same place as settings.py. And from each module I do a "from myproject.loggers import mail_logger as logger" and so on.</p> <p>But don't you think silently trapping exceptions like missing logger might be a recipe of future trouble. Least you should do when silently dropping errors is to log it, here you can't even do that.</p> Nice tip.

I tend to store all my logging related settings to loggers.py and loggers.cfg in the same place as settings.py. And from each module I do a “from myproject.loggers import mail_logger as logger” and so on.

But don’t you think silently trapping exceptions like missing logger might be a recipe of future trouble. Least you should do when silently dropping errors is to log it, here you can’t even do that.

]]>