Message346036
This is not actually a bug, but happens because the logger is instantiated directly, rather than through logging.getLogger(...). Because of the direct instantiation, the logger cache isn't tracked via setLevel() - because the logger doesn't end up in logging.manager.loggerDict.
However, I will incorporate Karthikeyan's test (modified to avoid direct instantiation), and update the documentation to strengthen the information to avoid direct instantiation of loggers. |
|
Date |
User |
Action |
Args |
2019-06-19 10:12:42 | vinay.sajip | set | recipients:
+ vinay.sajip, xtreak, David Wang |
2019-06-19 10:12:42 | vinay.sajip | set | messageid: <1560939162.91.0.333326507329.issue37258@roundup.psfhosted.org> |
2019-06-19 10:12:42 | vinay.sajip | link | issue37258 messages |
2019-06-19 10:12:42 | vinay.sajip | create | |
|