[bind10-dev] single vs multi module for libdns++ python binding

[JINMEI Tatuya / 神明達哉]

When I wrote python binding for a new class of libdns++, this question
arose: "why do we use a single giant python module (currently named
'libdns_python')"?

For comparison, dnspython uses multiple (sub)modules for "message",
"name", "rrset", etc.  And, I felt it might be more convenient if we
want to define module specific functions (which are not class
methods).  It may also help separate the binding C++ source files per
functionality (= python "module").  On the other hand, if we want to
keep 1-to-1 relationship between C++ namespaces and python modules, I
see it makes sense to use the single, flat module (although I'm not
sure if there's a pragmatic benefit by having this relationship).

Is there any specific design decision on this point, or is this
something worth discussing?

---
JINMEI, Tatuya