From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id BF7886DE1763 for ; Tue, 12 Jan 2016 11:03:22 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.309 X-Spam-Level: X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[AWL=0.242, RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bWnAXwa2hC5C for ; Tue, 12 Jan 2016 11:03:20 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 3F7316DE1760 for ; Tue, 12 Jan 2016 11:03:20 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1aJ4Dm-0003MK-0c; Tue, 12 Jan 2016 14:03:10 -0500 Received: (nullmailer pid 20844 invoked by uid 1000); Tue, 12 Jan 2016 19:03:15 -0000 From: David Bremner To: notmuch@notmuchmail.org Subject: Re: Crash with Python bindings In-Reply-To: <8737u26cpg.fsf@zancas.localnet> References: <5694CA65.8010400@fastmail.net> <87bn8r54dz.fsf@zancas.localnet> <8737u26cpg.fsf@zancas.localnet> User-Agent: Notmuch/0.21+5~gca076ce (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Tue, 12 Jan 2016 15:03:15 -0400 Message-ID: <8760yy4o3w.fsf@tesseract.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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: Tue, 12 Jan 2016 19:03:23 -0000 David Bremner writes: >> No path means path=None, which stands for the path from >> ~/.notmuch-config. That's exactly what I want. Is there some reason not >> to rely on this mechanism? > > Oh sorry, I'm (obviously) not that familiar with the python bindings. Nothing to do with Konrad's crash, but I consider the fact that the python bindings read ~/.notmuch-config to be a kind of layering violation, since that file belongs to the CLI, while the bindings are supposed to provide access to libnotmuch. Whether this is a real problem or just an aesthetic one, I'm not sure, but I thought I'd mention it since we are thinking of various config related issues. Obviously the location of the database is not one of the things it makes sense to store in the database. I can imagine scenarios where the bindings might be usable without the CLI, but they seem fairly artificial so far, since it seems like almost everyone needs notmuch-new / notmuch-insert. d