RetroSearch Browse

Thu Dec 9 00:35:34 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-December/106603.html

Paul Moore <p.f.moore <at> gmail.com> writes:

> You misunderstand me. I know that's how those levels work. What I'm
> not sure about (and I think would be interesting and potentially
> useful information) is whether the individuals participating in this
> thread feel that liberal use of info and debug level logging in
> library code is useful. All the discussion thus far has been about
> warning and error levels (mainly because people seem less comfortable
> with the "suppress by default" approach for those levels, whereas it's
> natural for debug and info levels).

OK I see, sorry - I just didn't get that from your original choice of words. I'm
probably not firing on all cylinders right now :-)

> I guess I'm wondering what best practices for logging might be.
> (Actually, that might make the subject of an interesting blog posting,
> if you're looking for suggestions ).

Thanks for the suggestion, I'll think about posting on this topic after
ruminating on it for a bit.

Regards,

Vinay Sajip

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-December/106603.html below:

[Python-Dev] Using logging in the stdlib and its unit tests