Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Mar 2018 15:00:05 -0700
From:      Pete Wright <pete@nomadlogic.org>
To:        Guido Falsi <madpilot@FreeBSD.org>, "D.-C. M." <my-roaming-data@outlook.com>, "kde@FreeBSD.org" <kde@FreeBSD.org>
Cc:        "ports@FreeBSD.org" <ports@FreeBSD.org>
Subject:   Re: FreeBSD Port: py27-qt5-core / Py36-qt5-core
Message-ID:  <8b5a9d2d-3373-f164-9a1d-e3acf19e1ec9@nomadlogic.org>
In-Reply-To: <c600a76b-b01c-6a65-c0c4-ecb2bd7ff105@FreeBSD.org>
References:  <AM5PR0901MB1139637F840990FAB019C890A9AC0@AM5PR0901MB1139.eurprd09.prod.outlook.com> <c600a76b-b01c-6a65-c0c4-ecb2bd7ff105@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help


On 03/27/2018 14:49, Guido Falsi wrote:
> On 03/27/18 22:44, D.-C. M. wrote:
>> Hello,
>>
> Hi!
>
>>   
>>
>> At this moment, it is impossible to build side by side py27-qt5-core and
>> py36-qt5-core.
>>
>>   
>>
>> There is a collison on /usr/local/bin/pyuic
>>
>>   
>>
>> This is annoying… Python 27 is still the default, but become quite old now.
>>
> 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.  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.

-pete

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8b5a9d2d-3373-f164-9a1d-e3acf19e1ec9>