BIND 10 #1179: python interface for data source
BIND 10 Development
do-not-reply at isc.org
Wed Sep 7 08:58:53 UTC 2011
#1179: python interface for data source
-------------------------------------+-------------------------------------
Reporter: | Owner: jelte
jinmei | Status: assigned
Type: task | Milestone:
Priority: major | Sprint-20110927
Component: data | Resolution:
source | Sensitive: 0
Keywords: | Sub-Project: DNS
Defect Severity: N/A | Estimated Difficulty: 4
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
I couple of points that may be helpful:
- I suspect a straightforward implementation of this python wrapper
would need to get access to symbols (and perhaps class/structure
definitions also) defined in pydnspp.so, which would be very tricky
(or may be mostly impossible if we want to be portable). I
encountered this issue for the DNS ACL wrapper, and my resolution at
that time was to use an intermediate frontend written in Python that
converts pydnspp objects to other Python native objects via
serialization so that the C++ wrapper itself wouldn't have to use
pydnspp definitions directly. You may need to do the same thing (or
may find a better solution).
- I suggest considering the use of src/lib/util/python/pycppwrapper_util.h
to avoid various pitfalls of the Python C API (see the doc in the
file for more details). The mkpywrapper script with the template
C++ files may also be useful.
- To generate pydoc in the C++ wrapper code, you may find the conversion
script useful. See my message on bind10-dev:
https://lists.isc.org/pipermail/bind10-dev/2011-August/002603.html
--
Ticket URL: <http://bind10.isc.org/ticket/1179#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list