From owner-freebsd-python@FreeBSD.ORG Mon Sep 16 14:54:08 2013 Return-Path: Delivered-To: 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 6A398AD6; Mon, 16 Sep 2013 14:54:08 +0000 (UTC) (envelope-from trtrmitya@gmail.com) Received: from mail-bk0-x229.google.com (mail-bk0-x229.google.com [IPv6:2a00:1450:4008:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CEF97239A; Mon, 16 Sep 2013 14:54:07 +0000 (UTC) Received: by mail-bk0-f41.google.com with SMTP id na10so1643086bkb.0 for ; Mon, 16 Sep 2013 07:54:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=G0lwMwak12Ab0h5K7DPIq0ff+oWws9q7wh1QWycsKyc=; b=nBqy+bkDnEjv12SbL+Dr5GQiEwJc/U1M+zfSPcAd6/FHmMGsz7NvB51tbVNrSEdekd V3qHHV2P9wDj2Uokh4MIWtR8lyuJELpAe6lR4PkghhkGQlFyZKZm5s6ITGjrIiP/sqVl Mikzkz6vbXJS907FZtQdLJmrL5UWXXZqm0UejY3/MOQo2xLC8pkdmnth1LUXidmskLR+ O5q1VMZYbKpV1t+zZjlkHsl+SUdx1DA0fo00gG5roSG7rFqKSQQF7RHzUQ61J3BQo199 GLSHA5ZOrI3PNCvmagaaXc8BvjYNDeA6tDHixclMVLXTgoPxHn+EyJd2CZvgxWj0TpIc 2iRg== X-Received: by 10.205.86.199 with SMTP id at7mr25052309bkc.9.1379343246220; Mon, 16 Sep 2013 07:54:06 -0700 (PDT) Received: from ?IPv6:2a02:6b8::408:244f:5663:554b:b94? ([2a02:6b8:0:408:244f:5663:554b:b94]) by mx.google.com with ESMTPSA id kk2sm7928409bkb.10.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Sep 2013 07:54:05 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: [CFT] lang/python becoming a python binary wrapper From: Dmitry Sivachenko In-Reply-To: <20130802180059.GA1278@medusa.sysfault.org> Date: Mon, 16 Sep 2013 18:54:04 +0400 Content-Transfer-Encoding: quoted-printable Message-Id: <598601A1-A36E-40D0-8C64-B7892CF7F71F@gmail.com> References: <20130802180059.GA1278@medusa.sysfault.org> To: Marcus von Appen X-Mailer: Apple Mail (2.1510) Cc: 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: Mon, 16 Sep 2013 14:54:08 -0000 Hello, Imagine the following scenario: I have both python2 and python3 installed. I want python2 to be the default version (lang/python port installs = python -> python2.7, etc). Then I want to build another port with python3 dependency. I put USE_PYTHON=3D3.3+ in port's Makefile, but it depends on = lang/python which pulls python2.7 too. How can I build a python module with 3.X only dependency? Thanks. On 02.08.2013, at 22:00, Marcus von Appen wrote: > Dear all, >=20 > as discussed previously on this list, users would love to install the > same python for multiple python versions. >=20 > Besides other issues (which I'll summarize in a different mail), one > problem, especially for binary packages, are the "am I the default?" > assumptions of lang/pythonXX. >=20 > The attached patch moves that logic into lang/python, instead of > maintaining the IF_DEFAULT magic within the individual python ports. > This will allow binary packages to be installed side by side without = any > hacks, but also requires users, which are now happily using > /usr/local/bin/python (being created by lang/pythonXX) to install > lang/python explicitly (UPDATING entry should be sufficient). >=20 > If there are no objections, I'll commit the change on the next weekend > (09.08.+). Please take your time to test. If portmgr@ feels this might > be a bit risky (ports implying /usr/local/bin/python based on > lang/pythonXX), please issue an exp-run beforehand. >=20 > Cheers > Marcus