[issue45682] Nicer default logging format

Vinay Sajip added the comment: > They too could pass a format argument themselves rather then relying on the > default format never changing. Changes to the stdlib shouldn't require changing previously working code (sometimes months or years old) to fix breakage caused by new stdlib changes.

[issue45682] Nicer default logging format

Olaf van der Spek added the comment: > Except that people may have used the current basic format in, for example, > unit tests, and that code could break after a change like the one proposed. They too could pass a format argument themselves rather then relying on the default format never cha

[issue45682] Nicer default logging format

Vinay Sajip added the comment: > However in the case of logging, an argument could be made that changing the > default would have less impact. Except that people may have used the current basic format in, for example, unit tests, and that code could break after a change like the one proposed

[issue45682] Nicer default logging format

Change by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue45682] Nicer default logging format

Raymond Hettinger added the comment: Generally, we can't change defaults after an API has been published because it immediately affects the output for people who use that default. However in the case of logging, an argument could be made that changing the default would have less impact. --

[issue45682] Nicer default logging format

New submission from Olaf van der Spek : The default logging format will print something like: WARNING:root:Hello Python! Could it default to something like this instead? 2021-10-31 14:52:36,490 WARNING: Hello Python! logging.basicConfig(format='%(asctime)s %(levelname)s: %(message)s') loggin