BIND 10 #1053: ImportError: cannot import name log_config_update
BIND 10 Development
do-not-reply at isc.org
Fri Jun 24 14:32:15 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 jreed):
Replying to [comment:5 vorner]:
> I'm getting slightly lost. Do you have two parallel installs of two
versions and one is using files of the other, or you have just one install
where the old version was overwritten with newer one?
>
Same installation directory. New overwriting old.
> If it is the second, I agree that is bad. But using a different name
looks more wrong than these small problems, the name is to keep
consistency with C++ library and is staying forever, the problems are
temporary and just for the few brave people using it at this stage. But we
could find a workaround (like making sure the log directory doesn't exist
during install or putting something similar like the __init__.py used for
testing there).
We should not get into a habit of asking end-users to manually clean up.
(On a related note, I plan to make an automated builder that installs to
same prefix everytime and then attempts to run some from there.)
--
Ticket URL: <http://bind10.isc.org/ticket/1053#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list