RetroSearch Browse

Wed Dec 8 20:04:36 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-December/106588.html

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

> 
> On 8 December 2010 14:52, Nick Coghlan <ncoghlan <at> gmail.com> wrote:
> > As I see it, there aren't many cases at the *library* level where
> > logging errors is more appropriate than raising exceptions:
> 
> On a slightly tangential note, what do you think of the idea of
> library code including info or debug level logging? In effect, tracing
> and diagnostic code built in and available simply by changing the
> logging level?

That's how it works right now. You get info() and debug() messages sent via
calls in library code, just by changing the level of (say) the root logger.

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/106588.html below:

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