set log level from config file #798
No reviewers
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-12-15#798
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "loglevel"
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?
Read the log level settings from the "loglevel" value in the
"bitmessagesettings" section of the config file. The possible
values map directly to the ones allowed by the logger module:
DEBUG, INFO, WARNING, ERROR, CRITICAL
Only allow these values, and cast to upper case to be more easy
going in the settings.
I need to take a closer look to how the logging works, but on first glance it looks ok.
Logging was rewritten, now you can configure it via a separate config file.