On Jan 12, 2:19 am, Matthew Pounsett wrote:
> First, I'd like to be able to permit users to do more typical log
> rotation, based on their OS's log rotation handler, rather than
> rotating logs from inside an application. This is usually handled by
> signalling an application with a HUP, whereup
On Jan 12, 8:03 pm, K Richard Pixley wrote:
> Here's the confusion. Each log named __name__ is under the root logger.
> If you want them all, then catch them all with the root logger.
Thanks! I knew I was missing something obvious. Between you and Jean-
Michael Pichavant I've figured out wha
On 1/11/12 18:19 , Matthew Pounsett wrote:
Second, I'm trying to get a handle on how libraries are meant to
integrate with the applications that use them. The naming advice in
the advanced tutorial is to use __name__ to name loggers, and to allow
log messages to pass back up to the using applica
Matthew Pounsett wrote:
[snip]
Second, I'm trying to get a handle on how libraries are meant to
integrate with the applications that use them. The naming advice in
the advanced tutorial is to use __name__ to name loggers, and to allow
log messages to pass back up to the using application's logg
On Jan 11, 9:34 pm, Roy Smith wrote:
> What I would do is log to syslog (logging.handlers.SysLogHandler) and
> let syslog worry about rotating log files. Why reinvent the wheel?
Syslog is fine for an application run by an administrator, but isn't
an option for a user.
--
http://mail.python.org/
In article
<7dabf43f-3814-47b6-966a-1439f5654...@i6g2000vbk.googlegroups.com>,
Matthew Pounsett wrote:
> First, I'd like to be able to permit users to do more typical log
> rotation, based on their OS's log rotation handler, rather than
> rotating logs from inside an application. This is usual
