-
Notifications
You must be signed in to change notification settings - Fork 66
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
Use 'logging' module instead of 'print' #464
Labels
Comments
opsdep
pushed a commit
that referenced
this issue
Mar 3, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 3, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 3, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 3, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 3, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 3, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 3, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 4, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 4, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 10, 2021
opsdep
pushed a commit
that referenced
this issue
Mar 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In several places, ´print´ is used for log messages (for example in the constructor of the ´Nansat´ class). Loggers should be used everywhere, so that the destination (file, console, etc...) can be easily configured.
This will become more of a problem as we are going to use ´nansat´ in long-running applications, and not only in a "desktop environment".
The text was updated successfully, but these errors were encountered: