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:08:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
xiang.zhang: The use case I've found is that I often have logging enabled while writing code, and then want to shut it off once I've finished. This might not be everyone's use case, but this is a backwards-compatible change since it's currently a required argument. If there's a sensible default, I think this is it.

rhettinger: We could use sys.maxsize instead of logging.CRITICAL to disable any custom logging levels as well if this is a concern.
Date User Action Args
2016-10-25 03:08:39Al.Sweigartsetrecipients: + Al.Sweigart, rhettinger, vinay.sajip, xiang.zhang
2016-10-25 03:08:39Al.Sweigartsetmessageid: <>
2016-10-25 03:08:39Al.Sweigartlinkissue28524 messages
2016-10-25 03:08:39Al.Sweigartcreate