You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very verbose output with print statements should then be replaced with logger.debug(); less verbose but useful stuff with logger.info(); stuff that goes wrong that the user should know about even if they don't care about info() level stuff should be a logger.warning(), etc.
This will allow us to easily and programmatically redirect logging output, change logging verbosity, apply common styling to all log messages (add timestamps, blah).
Should we add a unit test to check for new PRs if they have exists print statement in the code? Although this would enforce it to test scripts as well.
Specifically, stick something like
at the t op of the module.
Very verbose output with print statements should then be replaced with
logger.debug()
; less verbose but useful stuff withlogger.info()
; stuff that goes wrong that the user should know about even if they don't care aboutinfo()
level stuff should be alogger.warning()
, etc.This will allow us to easily and programmatically redirect logging output, change logging verbosity, apply common styling to all log messages (add timestamps, blah).
See the Logging Cookbook and the logging module docs.
The text was updated successfully, but these errors were encountered: