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