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-11-06.02:19:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Setting up different configurations for dev/prod is a bit more complicated than I'd like for most projects. I'd instead just call logging.disable(logging.CRITICAL).

The entire point of this is just for the convenience of being able to disable logging messages by calling logging.disable() instead of logging.disable(logging.CRITICAL).

It's a two-line change, backwards compatible, and (imo) a sensible default. You call logging.disable() expecting it to disable logging. You might want to disable a lower level, but as the Google search shows, most people just want to disable all logging period.
Date User Action Args
2016-11-06 02:19:05Al.Sweigartsetrecipients: + Al.Sweigart, rhettinger, vinay.sajip, xiang.zhang
2016-11-06 02:19:04Al.Sweigartsetmessageid: <>
2016-11-06 02:19:04Al.Sweigartlinkissue28524 messages
2016-11-06 02:19:04Al.Sweigartcreate