> I just committed a big change to how logging is configured so that > everything is now piped through Python's logging module and is very > flexibly configurable via the config files. You can reroute access > logs with the "turbogears.access" logger.
Great. > If you look at a brand new quickstarted project, you'll see a fairly > large section of dev.cfg devoted to logging. I'm debating about moving > some of that out into turbogears.config (the handlers and formatter). > The advantage is smaller and less intimidating config files. The > disadvantage is that it's not as obvious to someone what to do if they > want to change things. Opinions? I'm not a fan of standard logging configuration syntax but good that at least it moved to separate log.cfg file. Given that "most people won't change defaults" and default format is so elaborate and "low-level" I'd like to see a more high-level logging configuration. How about having a couple of "coarse" log-related settings in config file and use log.cfg if they are missing? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
