BIND 10 #1053: ImportError: cannot import name log_config_update
BIND 10 Development
do-not-reply at isc.org
Tue Jun 28 01:54:07 UTC 2011
#1053: ImportError: cannot import name log_config_update
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: | Status: new
defect | Milestone: New Tasks
Priority: | Resolution:
blocker | Sensitive: 0
Component: | Sub-Project: Core
logging | Estimated Difficulty: 0.0
Keywords: | Total Hours: 0
Defect Severity: Very |
High |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
How about the attached patch?
It will draw an explicit attention for early adopters to the pitfall
when they first try to upgrade to an incomatible version (and will tell
them what is wrong and what should be done).
This is a hack, and considering we are still in a very early stage of
deployment (so keeping the source clean and simpler could be preferred
over ensuring complete backward compatibility), I think we can/should
remove this rule in a 2-3 releases later (we'll need a ticket not to
forget it).
--
Ticket URL: <http://bind10.isc.org/ticket/1053#comment:7>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list