On Sep 18, 5:21 pm, Eric Holscher <eric.holsc...@gmail.com> wrote: > 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]: > 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. >
The approach I'd recommend is to have loggers at module level, and more granular than that if and where needed. We don't have to follow this blindly and tool up everywhere all at once to the same extent - it can progress naturally as and when we tackle issues and feel that logging is a part of continuous improvement. I think that's the spirit in which Simon initially posted. >From a user's point of view, it should be easy for them to turn the verbosity up or down at a module level at least (for example, an individual view module somewhere in Django). By which I mean, it'd be most natural to express "where" in the application you want verbosity turned up or down by thinking about apps and individual modules in those apps. 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-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 -~----------~----~----~----~------~----~------~--~---
