From owner-freebsd-python@freebsd.org Mon Oct 17 11:48:59 2016 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16B6FC1536E for ; Mon, 17 Oct 2016 11:48:59 +0000 (UTC) (envelope-from rm@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 04B7129F for ; Mon, 17 Oct 2016 11:48:59 +0000 (UTC) (envelope-from rm@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0165AC1536D; Mon, 17 Oct 2016 11:48:59 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3928C1536C for ; Mon, 17 Oct 2016 11:48:58 +0000 (UTC) (envelope-from rm@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id DB44429B; Mon, 17 Oct 2016 11:48:58 +0000 (UTC) (envelope-from rm@FreeBSD.org) Received: from [127.0.0.1] (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 0365713AF; Mon, 17 Oct 2016 11:48:57 +0000 (UTC) (envelope-from rm@FreeBSD.org) Subject: Re: Introducing python3 into user system To: Gerhard Schmidt , python@FreeBSD.org References: <5893aa6d-5e29-81b5-9685-a04ab8260bcb@ze.tum.de> <60f3bedb-8f57-2703-7ee9-736fc26ff9d0@yandex.ru> Cc: Ruslan Makhmatkhanov From: Ruslan Makhmatkhanov Message-ID: <0bd51f3b-e03b-2ea8-5c7b-1d108e78f2da@FreeBSD.org> Date: Mon, 17 Oct 2016 14:46:46 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 11:48:59 -0000 Gerhard Schmidt wrote on 10/17/2016 14:27: > Am 17.10.2016 um 12:39 schrieb Ruslan Makhmatkhanov: >> Gerhard Schmidt wrote on 10/17/2016 11:07: >>> Am 16.10.2016 um 21:22 schrieb Ruslan Makhmatkhanov: >>>> - if port has a build dependency upon python and it can be built both >>>> with python2 and python3, force it to build with python3 >>>> - if some standalone application can be running both with python2 and >>>> python3 and it have equivalent python3 dependencies, force it to be run >>>> with python3 >>> >>> What do you mean by "force it"?. >> >> I mean set USES=python3.3+ for such ports. > > This will install python3.5 on this system regardless if there is a > working python2.x installation, which is exactly what is wrong. I am a > software developer who runs legacy systems on python2.7. Forcing ports > that are able to run with python2.7 to install python3.5 will most > probably break my systems. USES should always represent the minimum > requirement not something so feel is something it should use. I'm not sure how it will break anything if conditions, listed in my initial message are complied. Would you please elaborate on that and provide an example of such a breakage? python3.5 and python2.7 can co-exist. And I just want to remind that we are talking only about standalone applications now, with no external dependencies, and also about ports that use python only at build phase. > > Please do not break systems without a really good reason. This we can > discus in 4 years when support for python2 will end, but not until than. > > Not everyone has the freedom to run only shine new software on shine new > systems. > > Regards > Estartu As far I understand, we should do some preliminary work to make it happen. We can't turn 26k of ports to using python3 in one day at 1st of January 2020. -- Regards, Ruslan T.O.S. Of Reality