This seems like a symptom of a much bigger problem.  Shouldn't the
bindings be checking or coercing the type of *every* argument that
gets passed from the caller through to a ctypes-wrapped libnotmuch
function?  Otherwise, a simple type error in a caller, like passing a
number instead of a string to one of the Python methods, would likely
result in a segfault.

On Thu, Sep 15, 2011 at 1:41 PM, Martin Owens <doctormo@gmail.com> wrote:
> Hello Sebastian,
>
> I've attached a diff for some proposed changes to help make dealing with
> unicode and strings in the bindings more regular. I noticed some of the
> methods were protected and others were not.
>
> Let me know.
>
> Best Regards, Martin Owens
>
> On Thu, 2011-09-08 at 15:45 +0200, Sebastian Spaeth wrote:
>> I have to admit, I am not deep into the libnotmuch/xapian internals,
>> so
>> I might be the wrong person to ask (I just do some python bindings to
>> whatever libnotmuch provides).