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