BIND 10 #933: introduce a framework to convert from doxygen to pydoc

[BIND 10 Development]

#933: introduce a framework to convert from doxygen to pydoc
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  assigned
                       Type:         |             Milestone:
  enhancement                        |            Resolution:
                   Priority:         |             Sensitive:  0
  medium                             |           Sub-Project:  DNS
                  Component:         |  Estimated Difficulty:  0.0
  documentation                      |           Total Hours:  0
                   Keywords:         |
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:2 shane]:
 > I don't see the script attached here, but does this still make sense if
 we're planning on using doxygen for Python?

 Depending on what kind of documentation how we produce for the
 C++-based python APIs, this task may be moot.  I don't yet understand
 exactly how we "use doxygen for python" and whether it really makes
 sense though.

 In any case,

 > Possibly we can still use this approach for things like pydnspp which
 are simply wrappers for C++ code, of course.

 I believe it still makes sense to extract key information from the C++
 doxygen document for the corresponding python API, whether the
 resulting output is pydoc or something else.

-- 
Ticket URL: <http://bind10.isc.org/ticket/933#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development