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 Al.Sweigart, rhettinger, vinay.sajip, xiang.zhang
Date 2016-10-30.15:01:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 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.

You could do this by having a configuration which is quite verbose while doing development and then less verbose when in production mode.  Then if an issue crops up in production, verbosity could be temporarily turned up in the production configuration while diagnosing the issue, then turned down again later, without making code changes. Remember that verbosity can be set at the handler level too, which sometimes gives finer-grained control of logging verbosity.
Date User Action Args
2016-10-30 15:01:47vinay.sajipsetrecipients: + vinay.sajip, rhettinger, Al.Sweigart, xiang.zhang
2016-10-30 15:01:47vinay.sajipsetmessageid: <>
2016-10-30 15:01:47vinay.sajiplinkissue28524 messages
2016-10-30 15:01:47vinay.sajipcreate