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 maggyero
Recipients maggyero, vinay.sajip
Date 2019-03-18.08:33:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1552898033.86.0.922446365538.issue36318@roundup.psfhosted.org>
In-reply-to
Content
Actually people do this all the time, to deactivate the logging of some third-party libraries (me included). For instance:

* https://stackoverflow.com/questions/24344045/how-can-i-completely-remove-any-logging-from-requests-module-in-python
* https://stackoverflow.com/questions/34598952/how-to-disable-info-logging-from-a-third-party-module-in-python
* https://stackoverflow.com/questions/38102291/turn-off-logging-in-schedule-library

And currently we can only use either solution 2 or 3 with `logging.config.dictConfig` (which are more verbose and less explicit). We cannot use solution 1 with `logging.config.dictConfig`.

In addition, all public attributes in the `__init__` methods of the `logging.Formatter`, `logging.Handler` and `logging.Logger` classes can be set from `logging.config.dictConfig`, except the `disabled` attribute, which is inconsistent.
History
Date User Action Args
2019-03-18 08:33:53maggyerosetrecipients: + maggyero, vinay.sajip
2019-03-18 08:33:53maggyerosetmessageid: <1552898033.86.0.922446365538.issue36318@roundup.psfhosted.org>
2019-03-18 08:33:53maggyerolinkissue36318 messages
2019-03-18 08:33:53maggyerocreate