--- /dev/null
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 89956431FBD\r
+ for <notmuch@notmuchmail.org>; Mon, 15 Dec 2014 12:41:39 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+ autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 7oIK3xtx09yJ for <notmuch@notmuchmail.org>;\r
+ Mon, 15 Dec 2014 12:41:36 -0800 (PST)\r
+Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155])\r
+ (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 64BA5431FAF\r
+ for <notmuch@notmuchmail.org>; Mon, 15 Dec 2014 12:41:36 -0800 (PST)\r
+Received: from remotemail by yantan.tethera.net with local (Exim 4.80)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1Y0cSQ-0001ZA-Er; Mon, 15 Dec 2014 16:41:30 -0400\r
+Received: (nullmailer pid 405 invoked by uid 1000); Mon, 15 Dec 2014 20:41:24\r
+ -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Matt <mattator@gmail.com>, notmuch@notmuchmail.org\r
+Subject: Re: Python bindings and Xapian exceptions\r
+In-Reply-To: <loom.20141215T121709-488@post.gmane.org>\r
+References: <87k4q7s43v.fsf@ut.hh.sledj.net> <878w6gis5g.fsf@SSpaeth.de>\r
+ <871v70ril7.fsf@yoom.home.cworth.org> <871v70z0y5.fsf@SSpaeth.de>\r
+ <loom.20141215T121709-488@post.gmane.org>\r
+User-Agent: Notmuch/0.19+7~g5d7f7a6 (http://notmuchmail.org) Emacs/24.4.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Mon, 15 Dec 2014 21:41:24 +0100\r
+Message-ID: <87iohc7iiz.fsf@maritornes.cs.unb.ca>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 15 Dec 2014 20:41:39 -0000\r
+\r
+Matt <mattator@gmail.com> writes:\r
+\r
+>> > But for exceptions in general, yes the notmuch library does need to be\r
+>> > fixed to allow the caller of functions to distinguish between things\r
+>> > like "no matches found" and "an exception occurred, so it's unknown if\r
+>> > any messages match the search". That's a general class of library\r
+>> > interface bugs that all need to be fixed.\r
+>\r
+> I 've also hit this *API bug* and was wondering if a fix had been done since\r
+> then (I use notmuch 0.17) ? I found nothing on http://notmuchmail.org/news/ \r
+\r
+Can you be more specific? I'd say in general no thorough overhaul of\r
+error handling has happened, but if you can tell us what particular\r
+libnotmuch function (or the equivalient python binding) you are having\r
+trouble with, we may be able to give a more informative answer.\r
+\r
+d\r