Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging #32

Open
stefan-voelk opened this issue Nov 12, 2024 · 0 comments
Open

Logging #32

stefan-voelk opened this issue Nov 12, 2024 · 0 comments
Assignees
Labels
module: core Related to the core module type: discussion Questions, proposals and info that requires discussion

Comments

@stefan-voelk
Copy link
Collaborator

Python offers logging capability via the logging package. I understand that this package is flexible since different logging levels can be defined (INFO, DEBUG, WARNING, ERROR, CRITICAL) and the logging messages can be channeled to different outputs (stdout, file). However, the difference between raising an exception, logging and printing sometimes is not obvious. I think it needs a discussion when to use logging and when not, and possibly refactoring our code.
A first guideline when to use logging is this tutorial.

@stefan-voelk stefan-voelk added type: discussion Questions, proposals and info that requires discussion module: core Related to the core module labels Nov 12, 2024
@stefan-voelk stefan-voelk self-assigned this Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module: core Related to the core module type: discussion Questions, proposals and info that requires discussion
Projects
None yet
Development

No branches or pull requests

1 participant