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 ncoghlan
Recipients ncoghlan
Date 2015-03-06.02:12:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Issue #22936 added support for easily displaying local variables in tracebacks to the unittest and traceback modules.

Would it be worth also making this capability readily available in the logging APIs that display traceback messages?

The main argument against it is that automatically logging local variables in tracebacks is a *really* good way to introduce sensitive information leaks into your log messages. "Safe repr" type objects (which automatically mask sensitive details in __repr__()) can mitigate this, but we don't provide such an object in the standard library (not even for bytes, bytearray or str, which are the typical containers for potentially sensitive data like passwords).
Date User Action Args
2015-03-06 02:12:46ncoghlansetrecipients: + ncoghlan
2015-03-06 02:12:46ncoghlansetmessageid: <>
2015-03-06 02:12:46ncoghlanlinkissue23597 messages
2015-03-06 02:12:44ncoghlancreate