diff options
| author |   Chris Larson <chris_larson@mentor.com> | 2010-06-09 16:17:29 -0700 |
|---|---|---|
| committer | Chris Larson <chris_larson@mentor.com> | 2010-08-27 11:38:19 -0700 |
| commit | 47ca82397bc395b598c6b68b24cdee9e0d8a76d8 (patch) | |
| tree | 751db52d65e175260ecb06fcce150eaae9663cf7 /TODO | |
| parent | f7c181a0f6ab0b4d33bf80a0e24a788de441f82b (diff) | |
| download | bitbake-47ca82397bc395b598c6b68b24cdee9e0d8a76d8.tar.gz | |
Use the python logging module under the hood for bb.msg
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 20 |
1 files changed, 6 insertions, 14 deletions
@@ -17,20 +17,12 @@ - Leverage the python logging module - - Create a new logging Handler which instantiates MsgBase derived objects - and passes them along, either via bb.event or directly over the - appropriate queues to the other processes. - - Alter the bb.msg functions to use the logging module. - - Convert bb modules to stop using the bb.msg functions. - - Switch the messaging wrappers in the bb package to use the logging module - directly, as we'll be deprecating the bb.msg versions, but these should - stay around for the metadata to use. - - Deprecate the bb.msg functions. - - Do we want to use the logging module in any of the UIs, for local - messages, as well? If we do, we don't want those to use our handler which - sends the Msg events to the UI :) - Looks like we may be able to use removeHandler.. will have to see how it - interacts with parent/child loggers. +- Convert bb modules to stop using the bb.msg functions. +- Switch the messaging wrappers in the bb package to use the logging module + directly, as we'll be deprecating the bb.msg versions, but these should + stay around for the metadata to use. +- Deprecate the bb.msg functions. +- Should we use the logging module rather than print in the knotty ui? Long term, high impact: |