RetroSearch Browse

Sat Dec 11 13:06:40 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-December/106716.html

Nick Coghlan <ncoghlan <at> gmail.com> writes:

> the logging module is a tool to track what is happening in a program, not a
> tool for providing a console based UI.

That was certainly the thinking behind how it worked before my recent changes,
but I completely accept that it wasn't helpful in the concurrent.futures
scenario, and agree with the comments you made around this in your earlier
posts. However, what Antoine has said on this thread (and others have concurred)
leads me to believe that he wants to use it not purely as a tracking tool (as
I've termed it, "an adjunct to doing real work") but also as a tool to provide
program output (e.g. doing some of the program's real work, say by calling
error() to print an error message).

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

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