BIND 10 #1179: python interface for data source

[BIND 10 Development]

#1179: python interface for data source
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jelte
  jinmei                             |                Status:  reviewing
                       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      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jelte


Comment:

 Hello

 Replying to [comment:11 jelte]:
 > I've made it into a more general way (make a list of rrsets to expect,
 and
 > check them one by one on name, class, type, sorted rdata), instead of
 hoping
 > that to_text() returns the same). It does completely skip rdata for
 RRSIG
 > rrsets now; the API won't allow me to recreate rrsig data 'FAKEFAKEFAKE'
 :)

 How is that so? In works in C++ tests, who stops you from creating them?

 > I think we can make separate tasks for those. They should be pretty
 > small.

 OK, tomorrow is planning call, let's have few tasks ready for it.

 One comment to the code. What is the purpose of the smiley?
 {{{#!python
 expected_rrsets[:]
 }}}

 If you mean the whole list, the brackets don't need to be there.

-- 
Ticket URL: <https://bind10.isc.org/ticket/1179#comment:12>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development