Received-SPF: pass (google.com: domain of patricktotzke@googlemail.com
	designates 10.181.11.227 as permitted sender)
	client-ip=10.181.11.227; 
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: Patrick Totzke <patricktotzke@googlemail.com>
User-Agent: alot/0.21+
To: notmuch <notmuch@notmuchmail.org>
References: <20120221002921.8534.57091@thinkbox.jade-hamburg.de>
In-Reply-To: <20120221002921.8534.57091@thinkbox.jade-hamburg.de>
Message-ID: <20120221153542.29533.62958@megatron>
Subject: Re: notmuch as a shared object aka library knigge
Date: Tue, 21 Feb 2012 15:35:42 +0000
Precedence: list

Hi all,

Those of you with long enough backlog on the list to remember my rant (id:2=
0110626202733.GA26837@brick)
can guess my opion on this matter but just to be sure..

I am not much of an expert on libnotmuch internals but am using the python =
bindings extensively.
It feels super-strange using a python module that possibly writes to stderr=
 or any other descriptor
without me explicitly telling it to.
Also, if the library segfauls or calls exit, it essentially rips out the py=
thon interpreter underneath my code
without me being able to do any proper error handling.

I know that error handling on a library level is hard, juggling around with=
 bare C, talloc and Xapian.
But i can only strongly encourage any rewrite that ends in the python bindi=
ngs behaving more pythonic!

Cheers,
/p