From owner-freebsd-python@FreeBSD.ORG Tue Jul 30 12:32:57 2013 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 70DC98D1; Tue, 30 Jul 2013 12:32:57 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 205092E10; Tue, 30 Jul 2013 12:32:56 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1V496e-0003oK-7r; Tue, 30 Jul 2013 15:32:48 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: mva@freebsd.org Subject: Re: Dealing with 2.7 and 3.3 installations In-reply-to: <20130730141133.Horde.0f8kjfhXWCzbnDRbbd9DvA1@webmail.df.eu> References: <20130730095456.Horde.XlxQMdj5YU1hIxf6WAYZOQ2@webmail.df.eu> <20130730115536.Horde.hJnU1JcPQIOJUsZ_wn7oOw9@webmail.df.eu> <20130730141133.Horde.0f8kjfhXWCzbnDRbbd9DvA1@webmail.df.eu> Comments: In-reply-to Marcus von Appen message dated "Tue, 30 Jul 2013 14:11:33 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Jul 2013 15:32:47 +0300 From: Daniel Braniss Message-ID: Cc: David Demelier , bapt@freebsd.org, koobs@freebsd.org, freebsd-python@freebsd.org X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jul 2013 12:32:57 -0000 > Daniel Braniss : > > [...] > > > >> > >> So what you need is support for a python module installed for two different > >> python versions at the same time, correct? And this (right now) is not > >> supported, I am afraid. > > > > as I explained, probably not too well, the problem is in the install from > > ports. the check for the installed modules does not check, or > > incorrectly checks for the desired version. > > That's understood quite well, the (big) problem however are not the > site-packages, > but other data installed e.g. under /usr/local/share, .../bin, .../wherever, > which currently does not necessarily take the python version into account. > > x11-toolkits/py-gtk2 is a good example for such an issue. If you install it > for python2.7 , there are heaps of files, which would conflict/overwrite a > previous python3.2/3.3 installation and vice versa, making the port > unusable for > all your python installations except one (in the worst case). > > > setting FORCE_PKG_REGISTER is a workaround, because it does not > > do any deinstall. > > It only is for ports, which keep everything in site-packages or are at least > python-version aware. I understand that there is no magic bullet, but in this particular case, where the question 'is installed' has a bug, can/should be fixed. This does not solve modules that are only python2.7 ok, like py-ldap. cheers, danny