From owner-freebsd-python@FreeBSD.ORG  Mon Sep 16 15:24:51 2013
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
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 229477BF
 for <python@freebsd.org>; Mon, 16 Sep 2013 15:24:51 +0000 (UTC)
 (envelope-from mva@FreeBSD.org)
Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de
 [80.67.31.40])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id D1FA025BE
 for <python@freebsd.org>; Mon, 16 Sep 2013 15:24:50 +0000 (UTC)
Received: from [89.183.18.32] (helo=localhost)
 by smtprelay02.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256)
 (Exim 4.68) (envelope-from <mva@FreeBSD.org>)
 id 1VLadE-0003aE-8G; Mon, 16 Sep 2013 17:22:32 +0200
Date: Mon, 16 Sep 2013 17:22:31 +0200
From: Marcus von Appen <mva@FreeBSD.org>
To: Dmitry Sivachenko <trtrmitya@gmail.com>
Subject: Re: [CFT] lang/python becoming a python binary wrapper
Message-ID: <20130916152231.GA1391@medusa.sysfault.org>
Mail-Followup-To: Dmitry Sivachenko <trtrmitya@gmail.com>, python@freebsd.org
References: <20130802180059.GA1278@medusa.sysfault.org>
 <598601A1-A36E-40D0-8C64-B7892CF7F71F@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT"
Content-Disposition: inline
In-Reply-To: <598601A1-A36E-40D0-8C64-B7892CF7F71F@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Df-Sender: MTEyNTc0Mg==
Cc: python@freebsd.org
X-BeenThere: freebsd-python@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: Marcus von Appen <mva@FreeBSD.org>
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2013 15:24:51 -0000


--X1bOJ3K7DJ5YkBrT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On, Mon Sep 16, 2013, Dmitry Sivachenko wrote:

> 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=3.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?

Right now this can only be arranged with a hack in Mk/bsd.python.mk,
line 581 and following. Those pull in lang/python, since many ports
depend on bin/python, although they are only compatible with a specific
python version.
Solving this issue and making ports depend on lang/python2 OR
lang/python3 OR a specific python version is on the agenda, but will
take some time, since many ports, that python scripts, have to be checked.

We happily invite everyone to check ports for those issues, report back
to us or provide fixes to solve this faster ;-).

Cheers
Marcus

--X1bOJ3K7DJ5YkBrT
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)

iEYEARECAAYFAlI3IjcACgkQi68/ErJnpkefGACfZSOXTP7eKeDOoB9mjjHl0fDc
LfYAmwWNgiCdT0Rg50WgfGsAImcW7qCX
=yKvW
-----END PGP SIGNATURE-----

--X1bOJ3K7DJ5YkBrT--