________________________________
From: andy pugh <[email protected]>
Sent: May 12, 2021 9:51 AM
To: EMC developers <[email protected]>
Subject: Re: [Emc-developers] Fwd: Re: Proposal: Stop supporting Py2 and GTK2
in Master.
On Wed, 12 May 2021 at 08:00, Chris Morley <[email protected]>
wrote:
> >
> > I meant a 2.9 python 2 release before switching master to python3
>> I can see the argument, but I don't think that 2.9 is ready to be a proper
>> release. And we don't have a 2.9 release manager.
>> We could consider archiving a set of buildbot .debs as a rollback option
>> for anyone caught out by the switch, but master isn't called "2.9" for a
>> reason, it is not intended for use on any machine where continued operation
>> is critical.
I used the reference for a discussion point.
Maybe it isn't ready yet to be released but neither is it ready to be python3
only
so possibly we have time for either idea.
What I was trying to ask phill is if python2 disappeared tomorrow - would that
cause a bunch of pain to users of QtPlasmaC
(as it is only in master and I would guess no one is is using it with python3)
Trying to gauge the problem of breaking master.
Considering over the years we have kept master stable and released stable
branches on a glacier pace - I wouldn't be surprised if quite a few people
don't use master in production machines (whether that's advisable or not)
Even myself - my current development computer is python2 only - I would need to
upgrade my system to get all the required python3 libraries.
I just think should have a better plan then 'sometime someone will break master
for python3'
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
