nba-sql
nba-sql copied to clipboard
Use logger
Printing isn't great. Use the logger!
I want to give this a shot... what is the preferred desired approach?
I am thinking this is using the logging
lib right?
One could:
- Have a central file that takes care of logging and thus only one configuration
- Initialize the logger per class where it is used.
- This means more verbose but one can name each logger and configure them case-by-case
I like the first approach and one can always add more parameters to be logged if necessary