➜

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 vstinner
Recipients vinay.sajip, vstinner
Date 2017-10-09.13:10:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507554629.31.0.213398074469.issue31732@psf.upfronthosting.co.za>
In-reply-to
Content 
Other references to a TRACE logging level:

* SaltStack: trace = 5
  https://docs.saltstack.com/en/latest/ref/configuration/logging/#log-levels

* autologging.TRACE = 1: "A custom tracing log level, lower in severity than logging.DEBUG."
  autologging: "Autologging eliminates boilerplate logging setup code and tracing code, and provides a means to separate application logging from program flow and data tracing."
  http://pythonhosted.org/Autologging/autologging.html#autologging.TRACE

* robot.logger.TRACE and robot.logger.trace()
  https://robot-framework.readthedocs.io/en/2.9.2/_modules/robot/api/logger.html
  https://robot-framework.readthedocs.io/en/2.9.2/autodoc/robot.api.html#log-levels

* "I'd like to have loglevel TRACE (5) for my application (...)"
  https://stackoverflow.com/questions/2183233/how-to-add-a-custom-loglevel-to-pythons-logging-facility

--


FYI while searching users of "TRACE" log level, I also found the other log levels:

* "NOTE" < DEBUG
* "FATAL" = CRITICAL
* "profile" = 15 < INFO, but 15 > DEBUG
* "garbage" = 1 < DEBUG

Again, I don't think that these ones are interesting.
History
Date User Action Args
2017-10-09 13:10:29vstinnersetrecipients: + vstinner, vinay.sajip
2017-10-09 13:10:29vstinnersetmessageid: <1507554629.31.0.213398074469.issue31732@psf.upfronthosting.co.za>
2017-10-09 13:10:29vstinnerlinkissue31732 messages
2017-10-09 13:10:29vstinnercreate