This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gjb1002
Recipients gjb1002, vinay.sajip
Date 2009-06-07.19:23:13
SpamBayes Score 2.6216525e-09
Marked as misclassified No
Message-id <1244402596.08.0.206967136762.issue6136@psf.upfronthosting.co.za>
In-reply-to
Content
If it was never intended for end users, then perhaps you could rename
this request as "provide an end-user-friendly log configuration format"
(that would live alongside the current one). It's hardly unusual that
users should be able to troubleshoot systems themselves by requesting
more (or different) logging, is it?

For example, log4py's format looked like this:
[my_logger]
LogLevel: Normal
Target: my_filename.log

Pretty much anyone can edit a bunch of sections that look like that
(with optional extras such as formatting where appropriate).

------------------------

As for mentions of this issue online, I linked to one such on my
comp.lang.python posting. It isn't recent, but the points about the
config file still apply as it hasn't substantially changed since then as
far as I can see. 3 different users raise essentially the same point
(and you also contributed to this thread)

http://www.mechanicalcat.net/richard/log/Python/Simple_usage_of_Python_s_logging_module

Here's another (only some of the discussion is relevant, but this exact
point is raised by the original poster and agreed with by the responder):

http://markmail.org/message/amxocg2nskd72qaf
History
Date User Action Args
2009-06-07 19:23:16gjb1002setrecipients: + gjb1002, vinay.sajip
2009-06-07 19:23:16gjb1002setmessageid: <1244402596.08.0.206967136762.issue6136@psf.upfronthosting.co.za>
2009-06-07 19:23:14gjb1002linkissue6136 messages
2009-06-07 19:23:13gjb1002create