Vinay Sajip added the comment:
- Original Message
> Mickey Killianey added the comment:
>
> Or were you suggesting logging.basicConfig? The limitation of basicConfig
>seems to be that it only works on an unconfigured root logger, not on a named
>logger, and it doesn't work if a
Mickey Killianey added the comment:
Vinay: thanks for the response.
My use case is that I've inherited a legacy application with a problematic
third-party module (call it 'foo'). I want to sprinkle in some file-logging
for the 'foo' logger to trace what's going on, while making the minimal
Vinay Sajip added the comment:
If I did this for some but not handler classes, then people would probably log
issues saying e.g. "Why doesn't NTEventLogHandler" support a level argument?
Other handlers do." etc.
What's the big problem with using setLevel() to set the level? If you're after
c
Mickey Killianey added the comment:
Would you be willing to consider supporting the level keyword as a convenience
for the most simple/common Handlers? (For example, maybe just StreamHandler
and FileHandler?)
--
nosy: +Mickey.Killianey
___
Python
