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 82E8C6DE0EED for ; Thu, 15 Aug 2019 02:53:26 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.149 X-Spam-Level: X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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 1PBFdNQfLLwA for ; Thu, 15 Aug 2019 02:53:25 -0700 (PDT) Received: from mail-ed1-f48.google.com (mail-ed1-f48.google.com [209.85.208.48]) by arlo.cworth.org (Postfix) with ESMTPS id 72DF66DE0EE3 for ; Thu, 15 Aug 2019 02:53:25 -0700 (PDT) Received: by mail-ed1-f48.google.com with SMTP id f22so1663894edt.4 for ; Thu, 15 Aug 2019 02:53:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:subject:in-reply-to:references:date:message-id :mime-version; bh=shFrlQw/Rb7Fv1kHw5UOTrcLNTMOu8o35vQi8wo4LIg=; b=U5ivEJTBGD7LlJQymYFulqKnNF4CMnqbQPX6DrSyoKAmFlDeR+dQM3X5oN6bTYEUxY MsrJ+h27UcLeeDC8+KBOlm2KgCVE1TEb6HSshSKOmwnVGqWhIdN6XVqq1EYUwAgS69Xq D6/jKuMgQeh9y33jiWjDXkMYgUjP7rHKkpiEZQmPygTkThYpWRxYHrqd/ur2xNhGJqZB 2kPO73LRfT8a4KOduv3h+7NtlYg8U6cEMBbB8EzaraGpTxqFhaFZ6+fY23M4CL8Y4jnO R8xqH+Br8BZvNb1ClNLMrwAUdl7C6OtRT+feOMG27Bzv2+vWR5I9mq/qYE9b6uEsq9Ni VmVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:subject:in-reply-to:references :date:message-id:mime-version; bh=shFrlQw/Rb7Fv1kHw5UOTrcLNTMOu8o35vQi8wo4LIg=; b=P0G/9l4vGSnyNT+pxp/LivJzKT4Jyl/t8kBl/8ikS7R3gk3x6mxtMU1NlC5OUzAGlA m5VsXE9cmRZPRuN1hpWbvbu20gwEfR/3qb4k6n2v9UNnoJUcfV+dyeC2fw1m8R5N2moH FGtADFNnfhkFDrGy9/70OHhzZjAbjuXNobEqOYH8YaEJZW0puDBvpdR8IMWKfqP4YIqU 69julgjZ5zyUX8H4ybI+M7DtNUJWcLF1VnGg+Y2bY7J5thRpaAmTT8H1TnQOYd1E0JaO PgZgaGl3NYMzGRrpIJcfXVqydKkMVOdhYXD0vfNEmxCHJ7i/pIVx/Uwr/2SfBR84R6Iu lc1Q== X-Gm-Message-State: APjAAAW1HOmqdajz64+lbwgKKNZ0KfQclqJ7pY3ODKv5NZkrzA0wLk36 Y2mKqKt6SrJd4elBFT3m8b4= X-Google-Smtp-Source: APXvYqwQxjJ6O3A4llSFA+YotSZLG8iLIgrQQdugSks1eMRue462K6Cz1B0F+EdQX3U0BJr//G830A== X-Received: by 2002:aa7:c508:: with SMTP id o8mr4380149edq.123.1565862803074; Thu, 15 Aug 2019 02:53:23 -0700 (PDT) Received: from powell.devork.be ([2a02:168:59e9::7a3]) by smtp.gmail.com with ESMTPSA id t12sm469048edw.40.2019.08.15.02.53.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 15 Aug 2019 02:53:22 -0700 (PDT) Sender: Floris Bruynooghe Received: (nullmailer pid 27691 invoked by uid 1000); Thu, 15 Aug 2019 09:53:21 -0000 From: Floris Bruynooghe To: David Bremner , notmuch@notmuchmail.org Subject: Re: segfault using python bindings In-Reply-To: <87d0h7ftaq.fsf@tethera.net> References: <154177495352.5588.12072713055654441286@x1.localdomain> <87lg5z74l3.fsf@tethera.net> <87o9aqhwnm.fsf@powell.devork.be> <87d0h7ftaq.fsf@tethera.net> Date: Thu, 15 Aug 2019 11:53:21 +0200 Message-ID: <87tvaivjou.fsf@powell.devork.be> 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: Thu, 15 Aug 2019 09:53:26 -0000 On Wed 14 Aug 2019 at 16:20 -0300, David Bremner wrote: > Floris Bruynooghe writes: > >> These are at https://github.com/flub/notmuch/tree/cffi/bindings/python-cffi >> >> I'm not really convinced of the way forward last time it was discussed >> on how to get them merged into notmuch itself so have failed to put in >> the not insignificant effort. >> >> I've since wondered if just getting them standalone on pypi is perhaps a >> useful service in the mean time as it's relatively little effort. And >> if there eventually is a desire again to get them merged in some way >> that could still be done. > > Can you remind me what the percieved blockers are for merging into the > main notmuch tree? I'm less hung up on python2 compatibility than I used > to be, fwiw. I'd be ok with shipping the old python2 bindings in contrib > for a bit for those who still need/want them, but concentrate our > maintenance effort on the cffi bindings. IIRC it was mostly about how to support transitioning from one API to the other since currently there's no compatibility. I guess there's nothing stopping one from using both APIs in one codebase though, AFAIK Xapian handles the required locking. But some of the discussions suggested being able to create a new Message object from an old one etc, allowing you to do more mixing during a transition period. This is the part that I said is possible but a lot of work and questionable if no one thought they'd be using it. Cheers, Floris