Hello,

I'd like to raise a question of logging policy for the TurboGears itself.

TurboGears uses logging both to help troubleshoot the framework itself and to 
notify user of important events. There is nothing wrong with this. OTOH, user 
should have the option to mute framework logging and be reasonably sure that 
this won't result in important messages being ignored. 

To be able to do this, there should be a documented policy that is obeyed by 
the framework authors. E.g. use DEBUG level for information that is of interest 
to framework developers and INFO and up for information that may be of interest 
to framework users. Or, use DEBUG/INFO for "internal" use and WARNING and upper 
levels to communicate with user.

Exact details don’t matter as long as they are properly documented and followed 
by the code.

Of course, judging what may be of interest to user is sometimes moot but that's 
another matter.

Reply via email to