On 4/27/06, Jorge Godoy <[EMAIL PROTECTED]> wrote: > > 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.
Yeah, with reasonable configuration, we can now put useful logging messages throughout TurboGears code to help people troubleshoot problems. > 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?). TurboGears will not run on anything less than 2.3, and I'm far more concerned with providing a good experience for people using CPython than worrying about potential Jython users. > 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. That's a great idea. I'll have to fiddle with the code a little bit, but I think I can do that. Though I agree that a separate log.cfg would be nice, I'll probably drop them in app.cfg for now because that requires fewer changes. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
