BIND 10 #312: python msgq timeouts differ from c++ ones
BIND 10 Development
do-not-reply at isc.org
Wed Sep 15 12:54:39 UTC 2010
#312: python msgq timeouts differ from c++ ones
-------------------------+--------------------------------------------------
Reporter: jelte | Owner: jelte
Type: defect | Status: reviewing
Priority: major | Milestone: y2 6 month milestone
Component: msgq | Resolution:
Keywords: | Sensitive: 0
Estimatedhours: 0.0 | Hours: 0
Billable: 1 | Totalhours: 0
Internal: 0 |
-------------------------+--------------------------------------------------
Changes (by stephen):
* owner: stephen => jelte
Comment:
Branch taken at r2808
Version checked: r2916
Ignoring property changes, files changed were
'''src/lib/python/isc/cc/tests/session_test.py'''
'''src/lib/python/isc/cc/session.py'''
'''src/lib/python/isc/config/ccsession.py'''
'''src/lib/python/isc/config/tests/unittest_fakesession.py'''
'''src/lib/python/isc/config/cfgmgr.py'''
'''src/lib/dns/name.cc'''
'''src/bin/bindctl/bindcmd.py'''
'''src/bin/auth/Makefile.am'''
'''src/bin/zonemgr/zonemgr.py.in'''
'''src/bin/cmdctl/cmdctl.py.in'''
All these are OK
'''src/bin/xfrout/xfrout.py.in'''
OK, but two minor points:
a) Where an error message is constructed from the concatenation of two or
more strings, e.g.
{{{
sys.stderr.write("[b10-xfrout] Error creating xfrout,"
"is the configuration manager running?")
}}}
... there is sometimes a missing space at the join (e.g. the text output
by the example above will have no space after the comma). The example
listed is one of the changes made in this ticket, but there are a couple
of other examples in the file.
b) Some error messages in the file are output via print(), others are
output via sys.stderr.write().
--
Ticket URL: <http://bind10.isc.org/ticket/312#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list