BIND 10 #756: Python logging - produce API
BIND 10 Development
do-not-reply at isc.org
Fri Jun 10 11:44:19 UTC 2011
#756: Python logging - produce API
-------------------------------------+-------------------------------------
Reporter: | Owner: UnAssigned
stephen | Status: reviewing
Type: | Milestone:
enhancement | Sprint-20110614
Priority: major | Resolution:
Component: | Sensitive: 0
logging | Sub-Project: DNS
Keywords: | Estimated Difficulty: 4.0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => UnAssigned
* status: accepted => reviewing
Comment:
It should be ready for review.
The branch starts by removing original python/isc/log (and therefore
temporarily removing logging from xfrout), as I needed the python
interpretter to find my .so library, not the original directory.
Then there's series of commits implementing the actual API. There are only
few functions to initialize it or so on the module level and one class ‒
Logger. It doesn't cover the whole C++ API, but it should be enough to
produce logging.
Follows a merge of master to include some fixes and adaptation to changes
from there.
It is not possible to configure the logging yet. My plan is to (in a
different ticket) get the configuration data, convert it back to JSON and
pass it to the C++ configuration code, so only one entry point will be
needed for it.
I hope it is not much of a mess (there are two parts that are not really
straight-forward, one is parsing of the parameters of the logging methods,
as the PyArgs_parse thing doesn't support arbitrary number of arguments,
and other is sharing code of similar methods).
--
Ticket URL: <http://bind10.isc.org/ticket/756#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list