LogHandler fixture changes the logger log level instead of the handler
Bug #1244256 reported by
Attila Fazekas
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Python Fixtures |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
When using the fixtures.LogHandler fixture even with nuke_handlers=Flase option, it has a negative side effect to all other handlers.
The LogHandler fixture should not touches the loggers log level, because it cusses issues to all other logging Handler which want to log on a different logLevel.
The Handler's verbosity can be changed on the handler http://
without causing issues to the other handlers.
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| Changed in python-fixtures: | |
| status: | New → Incomplete |
To post a comment you must log in.
Hmm, I believe we need to change the logger as well, because if its filtering output the dev has asked for that would be a problem. We can restore it though afterwards (I thought we did already)