BIND 10 #2853: Python wrapper of data source extensions

[BIND 10 Development]

#2853: Python wrapper of data source extensions
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:  muks
                Type:  task          |                       Status:
            Priority:  medium        |  reviewing
           Component:  data source   |                    Milestone:
            Keywords:                |  Sprint-20130625
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  5             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |  shared memory data source
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => muks


Comment:

 Hello

 Replying to [comment:19 muks]:
 > > First, where is the `catch_load_error` thing? I can find it in
 documentation, but not in the code. Is it planned in future ticket?
 >
 > This is an argument to the C++ `ZoneWriter` constructor. On purpose,
 > it's not possible to directly construct a `ZoneWriter` using the
 > Python API. But the `ZoneWriter` API documentation indicates how the
 > methods behave for the corresponding constructor arguments.

 OK, maybe I wasn't clear what I mean. If I'm a python programmer and read
 the documentation, I read about `catch_load_error`. But I'm confused,
 because I don't see where I set that.

 So, I see three options of what happens:

  * There's no way a python programmer can set it and it is always created
 as false. Then the description about error string being returned is
 useless and confusing.
  * There's no way a python programmer can set it and it is always created
 as true. Then the error string is returned every time and it never throws.
 Also confusing.
  * There's some way to influence how it is created from python (even if
 not directly passing it to the constructor). But then, such way is not
 obvious.

 What is the case? Why is it documented the way it is?

 > > {{{#!python
 > > r"""
 > > }}}
 >
 > This indicates a "raw" string. It means that the backspace character is
 > not considered as an escape character and is included as-is, etc.

 Good to know such thing exists (I expect there's no backspace character,
 that you meant backslash, but that's irrelevant).

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