On 03/28/18 00:16, Pete Wright wrote:
>>> 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 accelera
Hi D.-C. M., hi others,
Am 27.03.2018 um 23:49 schrieb Guido Falsi:
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
On 03/27/2018 15:06, Guido Falsi wrote:
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
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 pytho
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 be
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.
>
