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 vinay.sajip
Recipients vinay.sajip
Date 2018-05-22.19:15:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527016559.5.0.682650639539.issue33606@psf.upfronthosting.co.za>
In-reply-to
Content
If a logger is disabled (by setting it's disabled attribute to True), the check for this is done late in the dispatch of the logging event - during the handle() call - rather than isEnabledFor(), which would short-circuit some processing. So the check for logger.disabled should be moved to isEnabledFor().

Credit to Abhijit Gadgil for raising this:

https://stackoverflow.com/questions/50453121/logger-disabled-check-much-later-in-python-logging-module-whats-the-rationale
History
Date User Action Args
2018-05-22 19:15:59vinay.sajipsetrecipients: + vinay.sajip
2018-05-22 19:15:59vinay.sajipsetmessageid: <1527016559.5.0.682650639539.issue33606@psf.upfronthosting.co.za>
2018-05-22 19:15:59vinay.sajiplinkissue33606 messages
2018-05-22 19:15:59vinay.sajipcreate