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 pmpp
Recipients pmpp, rhettinger, vinay.sajip, vstinner
Date 2017-10-13.05:21:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507872104.66.0.213398074469.issue31732@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry, i didn't mean to be rude. Just wanted to pick your attention because i think you miss the point:  logging as is it with its levels is perfect for *log messages*.
Review the typical usage shown and you'll see that tracing level is for logging tracebacks : the debug message is separate. Traces just don't fit on standard log output, they clutter and obviously have a format of their own. 
As a user i see TRACE as context for logging.exception when it has nothing to do with errors or verbosity.
History
Date User Action Args
2017-10-13 05:21:44pmppsetrecipients: + pmpp, rhettinger, vinay.sajip, vstinner
2017-10-13 05:21:44pmppsetmessageid: <1507872104.66.0.213398074469.issue31732@psf.upfronthosting.co.za>
2017-10-13 05:21:44pmpplinkissue31732 messages
2017-10-13 05:21:44pmppcreate