[issue6136] Make logging configuration files easier to use

Changes by Vinay Sajip : -- assignee: -> vsajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: No feedback, closing. -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: There hasn't been any activity for around a month now - marking as pending, will close shortly unless there's some reason not to. -- resolution: -> wont fix status: open -> pending ___ Python tracker

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: "It was met by deafening silence though." Give it time - it's only been a few days. For some reason, Google Groups doesn't show your post in the first page of results when I search for logging configuration by date (i.e. most recent on top): http://groups.google.

[issue6136] Make logging configuration files easier to use

Geoffrey Bache added the comment: My comp.lang.python thread is here: http://groups.google.com/group/comp.lang.python/browse_thread/thread/a0c35c3c9ad210a4 It was met by deafening silence though. I don't see why a simple format would need to be customer-specific. log4py's isn't/wasn't and tha

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: "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 themsel

[issue6136] Make logging configuration files easier to use

Geoffrey Bache added the comment: 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 thems

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: "Who said anything about not supporting users who want the hierarchy? I'm talking about making "qualname" optional, not removing it entirely!" Ok, I see - sorry for the misunderstanding on my part. "... these files need to be read and edited by non-coders

[issue6136] Make logging configuration files easier to use

Geoffrey Bache added the comment: Who said anything about not supporting users who want the hierarchy? I'm talking about making "qualname" optional, not removing it entirely! I even supplied the entirety of the code (all 4 lines of it) to be clear what I meant a few comments ago. The fi

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: "As for (b), do you not think a large number of users will not bother with the hierarchical aspect of the logging framework? I'd say you need to be pretty advanced/large scale before that becomes interesting." I disagree with this. The hierarchical set up is one o

[issue6136] Make logging configuration files easier to use

Geoffrey Bache added the comment: OK, I hadn't seen the "delay" parameter until now. I guess this is new in Python 2.6? Good that there is already a way to avoid lots of empty files, though it'll be a while before I can assume Python 2.6 unfortunately... that probably renders point (a) moot. As

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: Re point a) and opening files - why not use the "delay" parameter on FileHandlers, which delays opening until a message is actually logged? I can understand why one wouldn't want empty log files cluttering up the place, but the same argument doesn't apply to socket

[issue6136] Make logging configuration files easier to use

Geoffrey Bache added the comment: OK, I'll take point (c) further on comp.lang.python. As for the others, it would be useful if you could at least understand my points. a) I'm aware that there isn't necessarily a one-to-one correspondence between loggers and files, don't see why that's relevant

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: a) Loggers don't have a one-to-one correspondence to files that are opened, so I don't quite understand your point. Perhaps you are conflating loggers with handlers. The common way of using logging is to have a small number of file-based handlers and perhaps a sock

[issue6136] Make logging configuration files easier to use

Geoffrey Bache added the comment: a) What is the point of opening files that will never be written to and sockets that will never be used? A large application might have a great many loggers for debugging which are off by default, and this means you have to either put up with lots of empty fil

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: Re. point (a): The configuration logic assumes that if you put things in the configuration file, you want them included - that means instantiating handlers, which will generally open their output files (uness the delay parameter is set) and sockets. If you use appe

[issue6136] Make logging configuration files easier to use

Changes by Antoine Pitrou : -- nosy: +vsajip priority: -> normal versions: +Python 2.7, Python 3.2 ___ Python tracker ___ ___ Python-b

[issue6136] Make logging configuration files easier to use

New submission from Geoffrey Bache : Recently tried to use the logging configuration file format as understood by logging.config.fileConfig() and found it very unwieldy for normal usage. I feel it needs to "scale down" better. Some thoughts: a) It creates handlers whether they're needed or not.