Calling getLogger results in an *atexit* hook related to a handler being
registered for the current Python process. It might also, depending on
its mood, print to stdout. These things make it miserable to actually
unit test any application which calls getLogger. See also
Chris McDonough wrote:
Calling getLogger results in an *atexit* hook related to a handler being
registered for the current Python process. It might also, depending on
its mood, print to stdout. These things make it miserable to actually
unit test any application which calls getLogger. See
On Fri, 2010-08-06 at 17:49 +0100, Chris Withers wrote:
Chris McDonough wrote:
Calling getLogger results in an *atexit* hook related to a handler being
registered for the current Python process. It might also, depending on
its mood, print to stdout. These things make it miserable to