I have looked into Logging before for another project, and I found that
SQLAlchemy's support seemed to be a pretty good model to follow. They define
all of their loggers under the sqlalchemy namespace, and then you can
configure different handlers for different things[1]:
import logging
logging.basicConfig()
logging.getLogger('sqlalchemy.engine').setLevel(logging.INFO)
logging.getLogger('sqlalchemy.orm.unitofwork').setLevel(logging.DEBUG)
I think that this would be necessary to have in Django, so that for
instance, I could listen to the django.orm logs, and not the django.http, or
listen to them with different handlers/levels.
Their implementation[2] is a little confusing to me, but I think that having
some prior art like this will allow us to better understand what we need,
and how to accomplish it, so I thought I would throw it out there.
1: http://www.sqlalchemy.org/docs/05/dbengine.html#configuring-logging
2:
http://www.sqlalchemy.org/trac/browser/sqlalchemy/trunk/lib/sqlalchemy/log.py
--
Eric Holscher
Web Developer at The World Company in Lawrence, Ks
http://ericholscher.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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
-~----------~----~----~----~------~----~------~--~---
