Date: Mon, 17 Oct 2016 12:55:59 +0200 From: "Vlad K." <vlad-fbsd@acheronmedia.com> To: freebsd-python@freebsd.org Subject: Re: Introducing python3 into user system Message-ID: <a544177ae6eac2d737adc531582351f7@acheronmedia.com> In-Reply-To: <bdbee544-64ed-0a87-2008-1817afa2baa2@FreeBSD.org> References: <c7c2d8eb-e512-b118-c432-25ca3ee094db@FreeBSD.org> <883cfb37-3946-aa2c-21d2-73a21ea3e365@FreeBSD.org> <d26ab706fbdee81e45046a2c724a132d@acheronmedia.com> <bdbee544-64ed-0a87-2008-1817afa2baa2@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-10-17 12:35, Ruslan Makhmatkhanov wrote: > > What I actually meant is to utilize USES=python:3.3+ for such ports, > to make it pick up default python3 version. Yeah I "misunderstood you correctly", heh, sorry I wanted to say two different things at once.... The only problem with that (and btw, please let's use 3.4+ because 3.3 is badly supported even upstream) is ports that are dependencies to python:2 ports. So those would have to be identified, which is the idea behind my continuous poudriere run. IMHO variants are the only thing that would help us force all that can go py3 to go py3, and build py2 in support for rdeps that require 2. Because right now it's a bit of a mess when you have such conflicting requirements. -- Vlad K.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a544177ae6eac2d737adc531582351f7>