config: add a default logging_format
#1714
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Without this option specified, we get the Python default format, which
is (among other problems) completely devoid of timestamp information.
This format, devised by Exirel while refactoring the logging mechanism,
outputs the timestamp, the package that generated the log line, the log
level of the line, and (finally) the actual message. Taking us from:
Registered 42 plugins, 0 failed, 0 disabled
to:
[2019-10-21 12:47:44,272] sopel.bot INFO - Registered 42 plugins, 0 failed, 0 disabled
Once this hits the stable release, it will become quite a bit easier to
follow along with bug reports!
Co-Authored-By: Exirel <florian.strzelecki@gmail.com>
|
You might want to add that information to the documentation page! |
|
Updating with more documentation. Rendered preview: |
Exirel
approved these changes
Oct 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without this option specified, we get the Python default format, which is (among other problems) completely devoid of timestamp information.
This format, devised by @Exirel while refactoring the logging mechanism, outputs the timestamp, the package that generated the log line, the log level of the line, and (finally) the actual message.
We'll go from:
to:
Once this hits the stable release, it will become quite a bit easier to follow along with bug reports!