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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
