Re: [chirp_devel] [PATCH 01/12] Fix chirp.logger module (#2347)

I will give it some thought. FWIW, I am planning to scour the code to convert prints to logging calls. After all, there shouldn't be any prints in the core chirp code; everything therein should some kind of logging message, right?

Lots of things can generate output on stdout/stderr, like poorly written libraries and such. If we direct that output to the logs without formatting, then we see it, but it's unformatted (and not timestamped).

So, IMHO, we should do it anyway.

--Dan