BIND 10 #1010: Configuration of the Python logging API

[BIND 10 Development]

#1010: Configuration of the Python logging API
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  stephen                            |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20110628
                  Component:         |            Resolution:
  logging                            |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  0.0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => UnAssigned
 * status:  assigned => reviewing


Comment:

 Ready for review.

 Python modules now have the same option to let logging config be handled
 automatically as c++ modules do when they create a ModuleCCSession.

 When handled automatically, the new module-level function
 isc.log.log_config_update is called, which in turn calls the same log
 config handler as the c++ version does (so apart from converting to c++,
 there is no python-specific parsing of the configuration data).

 Note that you can configure it, but right now no module actually uses it
 yet :) (i'll take up a ticket next to handle that)

 notable other changes:
 - renamed the c++ my_logconfig_handler to default_logconfig_handler and
 made it public
 - added (optional) config-update callbacks for remote modules in python
 (c++ already had this)
 - made the log/__init__.py a tad smarter (it found the wrong dir on my
 system)
 - added a function to convert from python basic types (which new_config
 and json-read data are in) to ElementPtr (currently only in ccsession.cc,
 if we find use for this elsewhere we should put it in a wrapper-util
 somewhere)

-- 
Ticket URL: <http://bind10.isc.org/ticket/1010#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development