| Issue 147: | Fixes for logging | |
| 1 person starred this issue and may be notified of changes. | Back to list |
I encountered there are several problems with logging. Attached patch addresses all these. 1. Config file errors are not reported as error messages and you have to enable debug level to spot them. 2. LogEvent events are not logged because they arrive in a tuple to observer and it does not expect it. 3. Exceptions while importing submodules are not logged unless in debug level (this is caused by fact that this event is not caught as an exception, but as a stderr output).
Dec 18, 2008
Your patch looks to me a bit wrong - eventDict['message'] is usually either
(LogEvent, ) or ('one line', 'second line', 'third line'). The change in git does not
seem to properly handle the latter situation.
Dec 18, 2008
Receiving of tuple by observer not causes exception. It shall write to log directly
as "('one line', 'second line', 'third line')"
Dec 18, 2008
You're right it works properly ... sorry for the mess.
Dec 18, 2008
Don't worry about it |
Owner: r000nster
Labels: Milestone-0.8.1.1