[Dev] logging proposal

[John Anderson]

Hi Everyone:

I looked over the logging proposal. I have a few personal biases on 
logging, which may be somewhat controversal, and consequently you may 
want to ignore some of my suggestion.

I find that adding lots of logging makes my code bigger that it needs to 
be, makes the code look ugly, slows it's execution and I often have a 
hard time wading through long logs, so as a rule I only do very minimal 
logging.

That said, I prefer a syngax that allows me to log something by adding 
the mininmum number of lines of code, and even the python syntax for 
logging seems a little too heavyweight for my tastes. I suspect that's 
why we end up with people using print instead of logging. However, I 
feel strongly that we should never be using printf and use logging 
instead, which makes it possible to turn on/off filter redirect etc.

I find it hard to come up with a sensable logging hiearchy, so if it 
were up to me, I'd probably leave it optional and just use a default, 
like file name paths or something else that's very simple. I generally 
find that there are  more levels of logging that I ever need, so keeping 
them to a very minimal set would be my preference.

Finally, if possible, I'd prefer a logging syntax with no more lines of 
code than printf, with maybe the exception of an extra import at the top 
of my Python file.

John


Kapil Thangavelu wrote:

> hi folks,
>
> i put together a logging proposal, about unifying the logging  
> configuration and usage within chandler,
>
> http://wiki.osafoundation.org/bin/view/Chandler/ 
> AlternativeLoggingProposal
>
> the structure of the logging hierarchy is a big open question..
>
> cheers,
>
> Kapil Thangavelu <hazmat at objectrealms.net>       Vision Implemented
> objectrealms.net <http://www.objectrealms.net>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev