Nice work, Yarin! You use a more decent way,
logging.getLogger(request.application), to achive app-wide logger. It is better
than my cache.ram() trick. Oh, I was so blind, man. :-)
And I wish GAEHandler and get_configured_logger() could go to web2py trunk, and
the scaffold's models/model.py contains just one extra line:
logger = get_configured_logger(folder = 'static', maxBytes=10240000,
backupCount=5)
so it will be even easier to use.
Best regards,
Iceberg, 2010-Aug-18, 02:20(AM), Wed
----------------------- Original Message -----------------------
From: Yarin <ykess...@gmail.com>
To: web2py-users <web2py@googlegroups.com>
Cc: iceb...@21cn.com
Date: Mon, 16 Aug 2010 13:31:16 -0700 (PDT)
Subject: Logging in web2py
-------------------
>
> I've posted an updated slice with an in-depth treatment of logging in
> web2py.
> http://web2pyslices.com/main/slices/take_slice/91
>
> Based on our earlier discussion
> http://groups.google.com/group/web2py/browse_thread/thread/d3b534113a904cd7/4d3f9f10d402210d?lnk=gst&q=logging#4d3f9f10d402210d
>
> The slice addresses the issues of application-level logging, once-only
> configuration, and simpler syntax. It offers an approach that fully
> leverages Python's native logging capabilities, allows for full
> flexibility in configuration, and doesn't interfere with existing
> logging implementations.
>
> Some notes:
> -I decided against creating a separate contrib module for the code as
> it would impede flexibility and obscure the simplicity of solution.
> If included in the framework, I think it should be as model code.
> -I abandoned the cache approach to creating singleton loggers, and
> just inspect handlers instead. (Logger caching was causing problems
> on GAE)
>
> Let me know what you think. Thanks Massimo, Iceberg...
