Feature #3668
Better organization for logging
Status: | Closed | Start date: | 04/25/2013 | |
---|---|---|---|---|
Priority: | Low | Due date: | 05/10/2013 | |
Assignee: | Stavros Sachtouris | % Done: | 100% |
|
Category: | kamaki | Spent time: | - | |
Target version: | v0.9 | Estimated time: | 5.00 hours |
Description
Please hierarchically organize the logger names for kamaki. The clients should be sub-loggers for the logger named "kamaki". This serves two purposes:
- As logger names are global, it will not conflict with other libraries using the name 'clients' as their global logger name. While no library is expected to have such a name, it is bad practice to do so.
- It will allow handling the logging verbosity and other features of the kamaki at its own isolation level by using the "kamaki" root logging. Users of the library can then mute kamaki's errors while keeping their own unmuted without explicitly going through all different client loggers.
Related issues
History
#1 Updated by Stavros Sachtouris almost 11 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
New name for http loggers:
kamaki.clients.recv kamaki.clients.send
There is now a (somewhat premitive) set of logging methods for kamaki: kamaki.logger
E.g.
from kamaki.logger import set_log_filename set_log_filename('my_filename.log')
#2 Updated by Stavros Sachtouris almost 11 years ago
- Due date set to 05/10/2013
- Estimated time set to 5.00
#3 Updated by Stavros Sachtouris almost 11 years ago
- Status changed from Resolved to Closed