1 Return-Path: <teythoon@jade-hamburg.de>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id DC987431FB6
\r
6 for <notmuch@notmuchmail.org>; Thu, 23 May 2013 07:42:27 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.804 tagged_above=-999 required=5
\r
12 tests=[DATE_IN_PAST_12_24=0.804] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id aO3eWP3ay2eH for <notmuch@notmuchmail.org>;
\r
16 Thu, 23 May 2013 07:42:19 -0700 (PDT)
\r
17 Received: from mail.cryptobitch.de (cryptobitch.de [88.198.7.68])
\r
18 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id 92276431FAF
\r
21 for <notmuch@notmuchmail.org>; Thu, 23 May 2013 07:42:19 -0700 (PDT)
\r
22 Received: from mail.jade-hamburg.de (mail.jade-hamburg.de [85.183.11.228])
\r
23 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
\r
24 (No client certificate requested)
\r
25 by mail.cryptobitch.de (Postfix) with ESMTPSA id 3F64E62E9F4
\r
26 for <notmuch@notmuchmail.org>; Thu, 23 May 2013 16:42:00 +0200 (CEST)
\r
27 Received: by mail.jade-hamburg.de (Postfix, from userid 401)
\r
28 id 9DF20DF2A2; Thu, 23 May 2013 16:41:59 +0200 (CEST)
\r
29 Received: from thinkbox.jade-hamburg.de (cryptobitch.de [88.198.7.68])
\r
30 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
\r
31 (No client certificate requested) (Authenticated sender: teythoon)
\r
32 by mail.jade-hamburg.de (Postfix) with ESMTPSA id 86674DF28B;
\r
33 Thu, 23 May 2013 16:41:56 +0200 (CEST)
\r
34 Received: from teythoon by thinkbox.jade-hamburg.de with local (Exim 4.80)
\r
35 (envelope-from <teythoon@thinkbox.jade-hamburg.de>)
\r
36 id 1UfCLm-0005Uq-RZ; Wed, 22 May 2013 18:57:18 +0200
\r
37 Content-Type: text/plain; charset="utf-8"
\r
39 Content-Transfer-Encoding: quoted-printable
\r
40 To: Patrick Gerken <notmuch@patrick-gerken.de>,
\r
41 From: Justus Winter <4winter@informatik.uni-hamburg.de>
\r
42 In-Reply-To: <20130522100830.30810.43576@mini>
\r
43 References: <20130520141459.30749.80963@mini> <87zjvp90xr.fsf@zancas.localnet>
\r
44 <20130521125402.9218.90558@thinkbox.jade-hamburg.de>
\r
45 <20130522100830.30810.43576@mini>
\r
46 Message-ID: <20130522165718.6823.71519@thinkbox.jade-hamburg.de>
\r
47 User-Agent: alot/0.3.4
\r
48 Subject: Re: Python Bindings missing on PyPI
\r
49 Date: Wed, 22 May 2013 18:57:18 +0200
\r
50 Cc: , notmuch mailing list <notmuch@notmuchmail.org>
\r
51 X-BeenThere: notmuch@notmuchmail.org
\r
52 X-Mailman-Version: 2.1.13
\r
54 List-Id: "Use and development of the notmuch mail system."
\r
55 <notmuch.notmuchmail.org>
\r
56 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
57 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
58 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
59 List-Post: <mailto:notmuch@notmuchmail.org>
\r
60 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
61 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
62 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
63 X-List-Received-Date: Thu, 23 May 2013 14:42:28 -0000
\r
65 Quoting Patrick Gerken (2013-05-22 12:08:30)
\r
66 > Quoting Justus Winter (2013-05-21 14:54:02)
\r
70 > > Quoting David Bremner (2013-05-20 16:32:32)
\r
71 > > > Patrick Gerken <notmuch@patrick-gerken.de> writes:
\r
72 > > I would not object to that, but David has a point here. If the version
\r
73 > > you get from pypi is newer than your libnotmuch, you will get errors
\r
77 > That is a point I did not consider much, I admit.
\r
80 > > Also I just looked at http://oswatershed.org/pkg/notmuch and
\r
81 > > http://oswatershed.org/pkg/python-notmuch . It looks like every
\r
82 > > distribution that is shipping libnotmuch packages also ships the
\r
83 > > python bindings. So everyone who got libnotmuch from their
\r
84 > > distribution can also obtain the appropriate bindings. And everyone
\r
85 > > who compiled notmuch also has the bindings. I'm just not sure what's
\r
89 > That is only partially true and this is entirely a python problem.
\r
92 > As a Python Developer I am forced to work in virtualenv, that isolate
\r
93 > the python running in there from system installed python packages.
\r
94 > That is necessary, because I cannot install two different versions
\r
95 > of the same package in python. Something that is essential when
\r
96 > working on multiple projects.
\r
99 > I tend to believe that virtualenv is a tool for developers and hosters,
\r
100 > but not for end users. I'd claim that it is their responsibility
\r
101 > to ensure the right version of libnotmuch.
\r
102 > Actually, I i were to deploy a python project with notmuch, I'd certainly
\r
103 > ensure that my deployment builds libnotmuch from source, something that
\r
104 > is not uncommon in the Plone world, which sets up projects with zc.buildo=
\r
108 > I'd love to hack on alot and afew, but I cannot install them safely on my
\r
109 > machines right now, they run in a little virtual machine just because of =
\r
112 Wouldn't it be better to install libnotmuch and the wrapper to this
\r
113 virtualenv so you make sure they match? I haven't used virtualenv, but
\r
114 searching the web turned up
\r
115 http://codersbuffet.blogspot.de/2009/09/wxpython-in-virtualenv.html
\r
116 . He uses a post activate hook to set the LD_LIBRARY_PATH
\r
117 variable. Maybe there's an even better way to do that now, seeing that
\r
118 his post is from 2009.
\r
120 > Based on my claim that pypi installations aren't usually done by end user=
\r
122 > does that reduce your reservations sufficiently to put the bindings on py=
\r
125 I don't have any reservations about anyone creating and maintaining an
\r
126 entry on pypi for notmuch. So if having an pypi entry helps you and
\r
127 potentially others as well, go ahead :)
\r
129 I'm concerned about potential API issues that won't crop up until
\r
130 someone runs some code. And someone would have to update and test the
\r
131 pypi entry, and that someone would have to be someone other than me
\r
132 since I've never used virtualenv or any method of deploying python
\r
133 software like pip or easy_install. I tend to install dependencies
\r
134 manually instead, and most of the time I don't have to do anything
\r
135 since most python software I use is usually packaged in Debian.
\r
projects / notmuch-archives.git / blob