This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vladmihaisima
Recipients vladmihaisima
Date 2021-12-10.15:58:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639151888.32.0.171616624845.issue46037@roundup.psfhosted.org>
In-reply-to
Content
When invoking logging.config.dictConfig - if a logger was previously disabled (for example by a call to "logging.config.dictConfig({'version': 1})") - the loggers specified in the dictionary will not be enabled.

Documentation at https://docs.python.org/3/library/logging.config.html specifies for disable_existing_loggers that "... behaviour is to disable any existing non-root loggers unless they or their ancestors are explicitly named in the logging configuration.". There is no explicit mention for what happens when a logger exists and is already disabled. I would have assumed that if present it will be enabled, but that does not seem to be the case.

So I think that if a logger is disabled invoking dictConfig cannot re-enable it.

See attached code for a reproducible case.
History
Date User Action Args
2021-12-10 15:58:08vladmihaisimasetrecipients: + vladmihaisima
2021-12-10 15:58:08vladmihaisimasetmessageid: <1639151888.32.0.171616624845.issue46037@roundup.psfhosted.org>
2021-12-10 15:58:08vladmihaisimalinkissue46037 messages
2021-12-10 15:58:08vladmihaisimacreate