Bitmessage/PyBitmessage-2025-02-25
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 54 Actions Packages Projects Releases 5 Wiki Activity

CLI option to specify logging level #1246

New Issue
Open
opened 2018-05-13 06:00:49 +02:00 by f97ada87 · 4 comments
f97ada87 commented 2018-05-13 06:00:49 +02:00 (Migrated from github.com)
Copy Link

It would be nice to have a command line option to specify or override log_level (debug/info/warning/error) at runtime. Useful when diagnosing transient issues like connectivity problems, object propagation etc.

It would be nice to have a command line option to specify or override log_level (debug/info/warning/error) at runtime. Useful when diagnosing transient issues like connectivity problems, object propagation etc.
PeterSurda commented 2018-05-13 10:08:14 +02:00 (Migrated from github.com)
Copy Link

You can configure logging in the file logging.dat which follows the python logger standard, here is the documentation: https://docs.python.org/2/library/logging.config.html#logging-config-fileformat

You can configure logging in the file `logging.dat` which follows the python logger standard, here is the documentation: https://docs.python.org/2/library/logging.config.html#logging-config-fileformat
f97ada87 commented 2018-05-13 12:16:19 +02:00 (Migrated from github.com)
Copy Link

Thanks Peter, I was aware of that capability, however editing syntax-heavy files is not the type of immediate flexibility that I had in mind, Anyway, I'm happy to not waste developer bandwidth with this at the moment if you think it's unimportant. If/when I have time, I'll write the PR myself.

Thanks Peter, I was aware of that capability, however _editing syntax-heavy files_ is not the type of _immediate_ flexibility that I had in mind, Anyway, I'm happy to not waste developer bandwidth with this at the moment if you think it's unimportant. If/when I have time, I'll write the PR myself.
PeterSurda commented 2018-05-13 12:56:19 +02:00 (Migrated from github.com)
Copy Link

Maybe a PR that would put a couple of examples into the logging contrib directory would help. Changing logging settings is more of a developer activity rather than an end-user activity so I don't think a command line switch is the best approach.

Maybe a PR that would put a couple of examples into the ~logging~ contrib directory would help. Changing logging settings is more of a developer activity rather than an end-user activity so I don't think a command line switch is the best approach.
dimyme commented 2018-09-20 12:05:11 +02:00 (Migrated from github.com)
Copy Link

the github wiki has info on logging

the github wiki has info on logging
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
documentation
Milestone
No items
No Milestone v0.6.5
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-25#1246
No description provided.
Delete Branch "%!s()"

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?