➜

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 Al.Sweigart
Recipients Al.Sweigart, rhettinger, vinay.sajip, xiang.zhang
Date 2016-10-25.03:35:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1477366511.06.0.666464118021.issue28524@psf.upfronthosting.co.za>
In-reply-to
Content 
> How about logger.disabled = True.

This seems to violate "there should be one and only one way to do it". What happens when logging.disabled is True but then logging.disable(logging.NOTSET) is called? I could see this being a gotcha.

Since logging.CRITICAL is 50, I think it's reasonable to assume that no one would create a logging level larger than sys.maxsize.
History
Date User Action Args
2016-10-25 03:35:11Al.Sweigartsetrecipients: + Al.Sweigart, rhettinger, vinay.sajip, xiang.zhang
2016-10-25 03:35:11Al.Sweigartsetmessageid: <1477366511.06.0.666464118021.issue28524@psf.upfronthosting.co.za>
2016-10-25 03:35:11Al.Sweigartlinkissue28524 messages
2016-10-25 03:35:10Al.Sweigartcreate