On Apr 29, 2010, at 7:22 AM, mdipierro wrote: > It may go in tools. What do other people think?
Logging is important enough for that, yes. WRT Keith's comment below: Python logging offers a rich collection of logging mechanisms, one of which is syslog, which in turn offers a rich collection of logging mechanisms. For many applications (including mine) we need unified logging with other processes, not necessarily Python. So syslog becomes the unifying mechanism for all our logging. I can see an argument for *not* using syslog, especially for self-contained apps that may not have access to syslog, or where you don't want to bother setting up a syslog environment. (What's the logging convention for GAE, btw?) > > On Apr 29, 8:37 am, Keith Edmunds <[email protected]> wrote: >> Hi Iceberg >> >>> But I would recommend you use a later version, quoted already in >>> Omicron's post. It uses RotatingFileHandler to avoid unstoppable log >>> file size >> >> Thanks for providing it. I can see the sense of your suggestion; however, >> I want the logging to be to the standard syslog files (which are >> logrotated independently). >> >> Massimo: I would have thought that application logging was an integral >> part of an enterprise application, much as authentication is, and should >> be in the scaffolding. It really isn't very big. >> >> Keith
