Use logging facility

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 issue names no files, tests, or entry points. Start by locating the Python code and cscore-related paths that emit messages, then determine the scope for configurable logging levels; done would mean consistent use of Python logging without unnecessary low-level logging overhead.

Written by the indexing model from the issue text.