[issue20345] Better logging defaults

Changes by Vinay Sajip : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue20345] Better logging defaults

Vinay Sajip added the comment: > Specifying the format is what requires mental investment (because for that I > need to read up on the config options). Not sure what you mean by config options. Is it too much to remember the format= parameter in your first post? I'm not planning to change the

[issue20345] Better logging defaults

Arne Babenhauserheide added the comment: (though calling logging.basicConfig() still produces some overhead, it does not pull me away from the task I’m currently doing) -- ___ Python tracker __

[issue20345] Better logging defaults

Arne Babenhauserheide added the comment: Just calling basicConfig() is not problematic. Specifying the format is what requires mental investment (because for that I need to read up on the config options). Would it be possible to add a simple way to select a certain logging style? In Mercurial

[issue20345] Better logging defaults

Vinay Sajip added the comment: > Can you give me a hint, how I could investigate that? There's no easy way - a lot of Python source is not available for public view, so there's no telling what the impact would be. While the use of the module-level functions is provided as a convenience, I don'

[issue20345] Better logging defaults

Arne Babenhauserheide added the comment: I do not think it is necessary to change the defaults, but I do think that it would help users of python. In the usecase of bigger applications, the default logging format does not matter: the overhead of logging.basicConfig() only happens once while th

[issue20345] Better logging defaults

Changes by Vinay Sajip : -- resolution: -> wont fix status: open -> pending type: -> enhancement versions: +Python 3.5 ___ Python tracker ___ __

[issue20345] Better logging defaults

Vinay Sajip added the comment: I don't think it is necessary or advisable to change the default, as it is very easy to provide your own format. As RDM has noted, this could affect backward compatibility. Furthermore, there are bound to be differing views of what an ideal default should be, so

[issue20345] Better logging defaults

R. David Murray added the comment: Well, you can always call basicConfig yourself...that's kind of the point of it. I'm guessing the current output was chosen exactly because it is pretty much just a print of the input to the log method. But I don't have strong feelings about it. On the oth

[issue20345] Better logging defaults

New submission from Arne Babenhauserheide: Currently the default operation of logging prints messages like the following: INFO:root: Milk found. This is close to a print-call, but not much more useful - especially not in small scripts. To make the default settings more useful to quick scripts,