Max, you bring up a really good point. When I added a little logging
code to Visit and Identity, I didn't really know what levels to set
each message at. The warning and error/exception level was pretty
obvious. But I didn't know if some messages were Info or Debug
because I didn't know who would be seeing them in production.
Clarifying this would help.
On 1 Feb, 2006, at 2:55 pm, Max Ischenko wrote:
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.
--
Jeff Watkins
http://newburyportion.com/
Getting an education was a bit like a communicable sexual disease. It
made you unsuitable for a lot of jobs and then you had the urge to
pass it on.
-- (Terry Pratchett, Hogfather)
