Em Quinta 27 Abril 2006 13:54, Kevin Dangoor escreveu: > 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.
VERY interesting. Specially to incentivate good practices. It is also a sign the there will be problems integrating TG with Jython, at least, because the logging "API" was introduce in Python 2.3. I dunnon how easy it is to wrap that to the logging API from Java, from which Python inherited some things (all of it?). > 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? > > My hunch is that people aren't generally going to change much from the > defaults. I'd put them on app.cfg or make a special log.cfg inside config depending on how big it is. I prefer smaller files, so I'd probably make it two files. Moving it there is needed because there are configurations that are common to both development and production mode. If we have good defaults -- on in development, off except for errors and warnings in production -- I don't believe people will notice or care for it if they don't want to. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
