Hi All,
Is there any reason why repoze.bfg.log:make_stream_logger manually
instantiates a logger rather than doing logging.getLogger(name)?
It makes it harder than it needs to be to replace the handlers of the
logger for unit testing purposes :-/
cheers,
Chris
___
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
http://plope.com/Members
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. Se
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
