The output is very chatty, especially progress reports from genetic.py. With most packages, one can apply logging filters outside the code to modify what information is surfaced. For instance, I normally would be able to do something like this in my calling code:
However, as this repo uses print statements instead of logging, this is not possible. Logging is generally best practice as you can control the look and style of the output, show timestamps, line numbers, set levels and so on.
trevorstephens
commented
1 year ago
The output is very chatty, especially progress reports from genetic.py. With most packages, one can apply logging filters outside the code to modify what information is surfaced. For instance, I normally would be able to do something like this in my calling code:
However, as this repo uses print statements instead of logging, this is not possible. Logging is generally best practice as you can control the look and style of the output, show timestamps, line numbers, set levels and so on.