On 10/23/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
> hey with regards to all this logging, as I expected people are having
> problems with my new logging setup already.
>
> I think what we're going to see mostly is that people who are already
> using logging for their programs have read the Python docs for the
> logging module, and set up their logging like this:
>
> import logging
> logging.basicConfig(level=logging.DEBUG)
> logging.debug('A debug message')
>
> since the above is configuring the root logger, it opens up all
> sqlalchemy logging up wide.
>
> So as I was writing the FAQ entry lecturing everyone to not open up
> their root loggers like that, it occured to me that i could just have
> sqlalchemy's config just do:
>
> logging.getLogger('sqlalchemy').setLevel(logging.ERROR)
>
> that way configuring the root logger would have no affect on SA's
> logging; youd still have to name SA's loggers explicitly.
>
> is that what turbogears does ? anyone see any downside to this ?
I don't know what TG does, but that's what I do in my own apps. Works fine.
--
Jonathan Ellis
http://spyced.blogspot.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sqlalchemy
-~----------~----~----~----~------~----~------~--~---
