From owner-freebsd-ports@freebsd.org Tue Mar 27 22:06:17 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86583F63397 for ; Tue, 27 Mar 2018 22:06:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1D99985850 for ; Tue, 27 Mar 2018 22:06:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id CE23DF63394; Tue, 27 Mar 2018 22:06:16 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB78BF63393 for ; Tue, 27 Mar 2018 22:06:16 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 54CEF8584C; Tue, 27 Mar 2018 22:06:16 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 409lTM1HHKzZtZ; Wed, 28 Mar 2018 00:06:15 +0200 (CEST) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id 7SWafidsSyBa; Wed, 28 Mar 2018 00:06:03 +0200 (CEST) Received: from tommy.madpilot.net (host190-122-dynamic.6-87-r.retail.telecomitalia.it [87.6.122.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.madpilot.net (Postfix) with ESMTPSA; Wed, 28 Mar 2018 00:06:03 +0200 (CEST) Subject: Re: FreeBSD Port: py27-qt5-core / Py36-qt5-core To: Pete Wright , "D.-C. M." , "kde@FreeBSD.org" Cc: "ports@FreeBSD.org" References: <8b5a9d2d-3373-f164-9a1d-e3acf19e1ec9@nomadlogic.org> From: Guido Falsi Message-ID: <71bf65f9-20ad-a30c-0fdd-bc78b31e666c@FreeBSD.org> Date: Wed, 28 Mar 2018 00:06:02 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <8b5a9d2d-3373-f164-9a1d-e3acf19e1ec9@nomadlogic.org> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 22:06:17 -0000 On 03/28/18 00:00, Pete Wright wrote: >> I'm not a python expert, but I understand that python 2.7 and python 3 >> are two slightly different languages not fully compatible with each >> other. >> >> I also understand(but have not gone into depth about this) that there is >> some resistance to python 3, with many developers being reluctant to >> move to version 3, for whatever reason(I imagine it's language design >> choices, but I really don't know) >> >> I'm stating this because it means such incompatibilities are not going >> away easily. It's not just a ports system problem, but an actual python >> ecosystem problem. >> >> Too say it in other words, python 2.7 isn't really just "the old >> version" and python 3 is not just "the new version". They have parallel >> lifes. > > I'm not %100 sure that's really an accurate assessment of the slow > uptake in Python3. I'd like to make it clear I don't know the details, I just stated what I heard. I know this could not be accurate. > Regardless, the clock is ticking on the 2.x codebase > as it is reaching EOL status in 2020: > > https://www.python.org/dev/peps/pep-0373/ > > Hopefully a solid deadline (which has already been pushed back) will > motivate developers to accelerate the task of migrating to py3 sooner > rather than later. Speaking strictly as the maintainer of the calibre port and having discovered just now about this deadline: I don't know what the calibre developer plans to do about this, I'm certainly unable to port calibre to python 3, so I will do the best to keep it working for as long as python 2.7 is available in the ports, or update the port to use python 3 once the upstream does port it to that version. -- Guido Falsi