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 8F82E6DE0226 for ; Sun, 11 Nov 2018 12:16:17 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.003 X-Spam-Level: X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[AWL=0.004, 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 2m9Lr_y9G78d for ; Sun, 11 Nov 2018 12:16:15 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 992F16DE0225 for ; Sun, 11 Nov 2018 12:16:15 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1gLw9R-0005ay-SW; Sun, 11 Nov 2018 15:16:09 -0500 Received: (nullmailer pid 32007 invoked by uid 1000); Sun, 11 Nov 2018 20:16:08 -0000 From: David Bremner To: David =?utf-8?B?xIxlcGVsw61r?= , notmuch@notmuchmail.org Subject: Re: segfault using python bindings In-Reply-To: <154177495352.5588.12072713055654441286@x1.localdomain> References: <154177495352.5588.12072713055654441286@x1.localdomain> Date: Sun, 11 Nov 2018 16:16:08 -0400 Message-ID: <87lg5z74l3.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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: Sun, 11 Nov 2018 20:16:17 -0000 David =C4=8Cepel=C3=ADk writes: > Hello Notmuch devs, > > I'm facing an issue trying to use the Python bindings. This trivial > piece of code segfaults: > > import notmuch I don't remember the details [1], but there are known conflicts between recent versions of python3 and the way the notmuch python bindings manage memory. So it could be that. There was also an initiative to rewrite at (python3 only?) version of the bindings that did not have this problem. I haven't heard much about that recently. [1]: There is some discussion in the list archives.