Use logging library #50
Labels
No Label
ANSIBLE
BUG
CODE
DEVELOPMENT
DOCUMENTATION
FEEDBACK
FIX
HOWTOs
IDEA
INFRA
ISSUE
MAILSERVER
TESTS
To-Be-Reviewed
WEB
WEBSITE
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/gpg-lacre#50
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Consider replacing custom logging code with Python
logging
module found in standard library functionality.See documentation.
Python's Logging HOWTO mentions
logging.config
package which makes it possible to just point at a file and load logging configuration from it, including formatters. I think that's the way to go.This flexibility comes at a cost: it makes things more complex.
The question we should answer is: what happens when logging configuration is missing? A reasonable default would be using syslog.
Things to consider:
This has been solved with #65.