-
Notifications
You must be signed in to change notification settings - Fork 212
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
improved logging facility #75
Conversation
|
||
logging.basicConfig() | ||
# set up logging to file | ||
logging.basicConfig(level=logging.INFO) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this turn on --verbose always?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I moved some stuff that we had set to info into debug, the idea being that we want the default output level to be more informational than warn.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, so logging.info(...) is something users will always see?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By default, yes. --silent turns it off.
1) Remove newlines from logger.info statements, it already adds them 2) Change test_name to a debug, it was adding too much clutter 3) Change run_cmd to support verbose flag properly
Closed, made new PR. |
Minor changes:
The logging facility now includes a -s, --silent option.
When a script is run at the --debug level it also creates a file scriptname.log
So there are now 4 levels of logging:
default (no option)
--silent
--verbose
--debug