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 360976DE0924 for ; Fri, 23 Aug 2019 05:07:23 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.053 X-Spam-Level: X-Spam-Status: No, score=-0.053 tagged_above=-999 required=5 tests=[AWL=-0.052, 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 tMO2KW6NTP3N for ; Fri, 23 Aug 2019 05:07:22 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 29F7B6DE0360 for ; Fri, 23 Aug 2019 05:07:21 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1i18LZ-0005VK-Qh; Fri, 23 Aug 2019 08:07:13 -0400 Received: (nullmailer pid 2506 invoked by uid 1000); Fri, 23 Aug 2019 12:07:12 -0000 From: David Bremner To: Daniel Kahn Gillmor , "Rollins, Jameson" , Floris Bruynooghe , "notmuch@notmuchmail.org" Subject: Re: segfault using python bindings In-Reply-To: <87y2zkbq1a.fsf@fifthhorseman.net> References: <154177495352.5588.12072713055654441286@x1.localdomain> <87lg5z74l3.fsf@tethera.net> <87o9aqhwnm.fsf@powell.devork.be> <87d0h7ftaq.fsf@tethera.net> <87tvaivjou.fsf@powell.devork.be> <871rxmfw9l.fsf@tethera.net> <87r25fvjmp.fsf@powell.devork.be> <8736huecc8.fsf@fifthhorseman.net> <87ef1dgg1a.fsf@tethera.net> <87zhk1gfeq.fsf@caltech.edu> <87y2zkbq1a.fsf@fifthhorseman.net> Date: Fri, 23 Aug 2019 09:07:12 -0300 Message-ID: <871rxcgk5r.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain 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: Fri, 23 Aug 2019 12:07:23 -0000 Daniel Kahn Gillmor writes: > The other possibility would be to implement the old "notmuch" API on top > of the new one with explicitly logged deprecations. But iirc, the > semantics and object lifecycle/ownership issues are subtly different > enough that this would be a non-trivial project. I'd be happy to be > wrong though, perhaps someone closer to the systems (someone actively > using the current python bindings on an ongoing project?) could look > more closely? IIUC, it is precisely this compatibility layer that has stalled things for a year or so. I don't think we can afford to wait longer. d