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
We should generally use the Python "logging" facility, although it might depend on what is done inside cscore and the related Python code.
logging let you have messages with different priority (debug, warning, etc) and you can set what is recorded. You can still send it to a file as needed.
One thing to remember though: if you have "logging.debug("foo")" everywhere, it will still slow down your code even if the "debug" messages are not saved. So low level logging code should still be used sparingly and/or commented out for "production".
The text was updated successfully, but these errors were encountered:
Definitely low priority.
We should generally use the Python "logging" facility, although it might depend on what is done inside cscore and the related Python code.
logging let you have messages with different priority (debug, warning, etc) and you can set what is recorded. You can still send it to a file as needed.
One thing to remember though: if you have "logging.debug("foo")" everywhere, it will still slow down your code even if the "debug" messages are not saved. So low level logging code should still be used sparingly and/or commented out for "production".
The text was updated successfully, but these errors were encountered: