BIND 10 #1103: catching import error in python libs

BIND 10 Development do-not-reply at isc.org
Mon Jul 11 16:33:41 UTC 2011


#1103: catching import error in python libs
-------------------------------------+-------------------------------------
            Reporter:  jelte         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 In some of the libraries, import errors (mainly for pydnspp, but also for
 a few others) are caught, at which point an error is printed. While
 converting to the new logging system we encountered a problem (see the
 comments in #763); the logging system is most likely not initialized

 More generally, we shouldn't just log an error, as this is a fatal problem
 (it'll crash the moment it needs said library anyway), so we should let it
 fail immediately anyway.

 src/lib/python/isc/notify/notify_out.py has a comment here now, but the
 rest of the libraries need to be checked as well.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1103>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list