Home | Trees | Indices | Help |
|
---|
|
A monostate class for run-time logging of messages. Just call Logger.addMessage() to log a message. To output messages to a file you just need to create an instance of a Logger object, and when that object falls out-of-scope the log file will be written. Alternatively, if the isVerbose option is set to False, then the log file will be written too continuously whilst an initialised Logger object is in scope.
|
|||
|
|||
|
|||
|
|||
Inherited from |
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
str, str |
|
||
|
|||
|
|||
|
|
|||
Inherited from |
|
Initialise a Logger object by setting the full path to the log file. The path is existed to make sure it exists, and if isVerbose is set to False then the log file is initialised with messages logged to date.
|
Reverts the log file path to the home directory in case of error.
|
Log the details of a trapped exception to the accumulating log file for a CU invocation. Also logs full trace-back information as to where the exception occurred (useful for programming errors).
To Do: This function is deprecated. Use addExceptionMessage() with the includeTrace flagged turned on instead. |
Logs a message from a raised exception.
|
Logs a message from a raised exception, that has been ignored.
|
Log a message. This is displayed to stdout if in "echoOn" mode, and also written to the log file if not in "isVerbose" mode.
|
Write all messages that have been currently logged.
|
Extracts useful information to be logged from a thrown exception. Includes some specific features for database exceptions.
|
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Mon Sep 8 15:46:54 2014 | http://epydoc.sourceforge.net |