From owner-freebsd-python@FreeBSD.ORG Tue Jul 30 14:28:17 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 89C59BE2; Tue, 30 Jul 2013 14:28:17 +0000 (UTC) (envelope-from mva@freebsd.org) Received: from smtprelay06.ispgateway.de (smtprelay06.ispgateway.de [80.67.31.96]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0458B2768; Tue, 30 Jul 2013 14:28:17 +0000 (UTC) Received: from [80.67.16.118] (helo=webmailfront01.ispgateway.de) by smtprelay06.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1V4AuH-0001Ot-67; Tue, 30 Jul 2013 16:28:09 +0200 Received: from his1.his.de (his1.his.de [192.124.237.237]) by webmail.df.eu (Horde Framework) with HTTP; Tue, 30 Jul 2013 16:28:09 +0200 Date: Tue, 30 Jul 2013 16:28:09 +0200 Message-ID: <20130730162809.Horde.R0wzwYBDdIJV7w9jpwmaVg1@webmail.df.eu> From: Marcus von Appen To: Daniel Braniss Subject: Re: Dealing with 2.7 and 3.3 installations References: <20130730095456.Horde.XlxQMdj5YU1hIxf6WAYZOQ2@webmail.df.eu> <20130730115536.Horde.hJnU1JcPQIOJUsZ_wn7oOw9@webmail.df.eu> <20130730141133.Horde.0f8kjfhXWCzbnDRbbd9DvA1@webmail.df.eu> In-Reply-To: User-Agent: Internet Messaging Program (IMP) H5 (6.0.4) Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline X-Df-Sender: ZnJlZWJzZEBzeXNmYXVsdC5vcmc= 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 Reply-To: mva@freebsd.org List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jul 2013 14:28:17 -0000 Daniel Braniss : >> 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. Even that is not as trivial as it might sound at the first glance, since it could result in patching a lot of ports for something that feels a it incomplete. The bottom line is (speaking personally here): a quick solution cannot be provided, but that does not mean that your issue is rejected or ignored. Providing parallel installation support for different python versions just needs to be edged out a bit more, including how to deal with the different types of ports being around. Cheers Marcus