On 2021-05-11 11:01 p.m., Phill Carter wrote:

On 12 May 2021, at 3:47 pm, Chris Morley <[email protected]> wrote:

I copied this from github (and added to):

I don't think anyone really thinks we can/should keep supporting py2 in the 
future.
The real questions are how/when will we transition - as the transition will be 
very disruptive.
Will we do a final py2 release first? QtPlasmac might appreciate this (or is 
2.8 mostly the same?)
QtPlasmaC is not in 2.8.

Would releasing a python2 version of QtPlamaC be desirable in your opinion?

Do very many people use QtPlasmac in production situations right now?

Have you tested QtPlasmac in python3?

Will we wait until we have every program converted to py3?
What will we do for programs not converted? remove the code? just remove from 
build?
For PlasmaC, the intention at this stage is to remove it from master when the 
py3 changover happens then users that want to stay with the latest master can 
migrate to QtPlasmaC. (PlasmaC will stay in 2.8)

That seems reasonable as there is an upgrade path.

How will we warning/inform users (in production/semi-production) of master that 
we will break everything.
Keeping in mind if a user is using master in older distributions, it may 
require the user to upgrade to a new distribution to have python3 support.
We should start warning people soon - what is the best way?
I jumped the gun and made a start here 
<https://forum.linuxcnc.org/plasmac/42524-important-notice-for-plasmac-users#208609>
I saw that! We need to target a time to make it more useful, but that lets people most affected to discuss it more broadly



_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to