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 7E1306DE0228 for ; Wed, 4 Apr 2018 18:09:55 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 yOtreM8UXhmU for ; Wed, 4 Apr 2018 18:09:54 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 774BC6DE0227 for ; Wed, 4 Apr 2018 18:09:54 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1f3tPT-00043E-5c; Wed, 04 Apr 2018 21:09:51 -0400 Received: (nullmailer pid 10389 invoked by uid 1000); Thu, 05 Apr 2018 01:09:49 -0000 From: David Bremner To: Brian May , notmuch@notmuchmail.org Subject: Pypi In-Reply-To: <871sfuegxp.fsf@silverfish.pri> References: <5694CA65.8010400@fastmail.net> <20160112102329.4269.20741@thinkbox.jade-hamburg.de> <20160112185107.GA21580@odin.tremily.us> <87k1ucp6xb.fsf@tethera.net> <87po3x4tuc.fsf@thinkbox.jade-hamburg.de> <87bmf8fyy8.fsf@silverfish.pri> <87k1twco4w.fsf@tesseract.cs.unb.ca> <878tabg73f.fsf@silverfish.pri> <87in9f94l0.fsf@tethera.net> <871sfuegxp.fsf@silverfish.pri> Date: Wed, 04 Apr 2018 22:09:49 -0300 Message-ID: <878ta2jw6a.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.26 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, 05 Apr 2018 01:09:55 -0000 Brian May writes: > Ideally the python bindings should be in a git repository that is > separate from the C library. This means you don't have to release new > python bindings for every new source code release of notmuch. You only > need to make a new release if supporting new features or a new release > that breaks backword compatability. It also will make it easier to build > the python libraries standalone using the installed versions of the C > library, which I suspect might make pypi support a lot easier. Currently the notmuch test suite uses (and tests) the python bindings. Having the notmuch library build-depend on a seperate python bindings package would create (I think) a circular build dependency. Splitting the repo would also break all the existing distro packaging of the bindings (e.g. for debian). So, not extremely keen to do that, at the moment. d