On Tue, 2022-11-22 at 19:03 +0100, Alexander Kanavin wrote: > The serious need is that we need to patch all the scripts that ask > for python to add a 3 to it. And there will be more of these going > forward, not less. I’d rather just always have python available. Not > a problem worth deliberating over to be honest.
I don't think it is that simple. a) If we take the change, we're no longer explicit in what we're using which means users can be taken by surprise when a python2 script finds python3 and could sometimes break. b) Our current approach means that people have at least looked at and decided something is python3 safe. c) It means that anyone still using python2 components is left with no way to make things work. Whilst nobody should be using python2 anymore, I suspect some still are and this will be a huge problem to them. d) If there ever is a python4, we'll have to redo a lot of the work we're done to reach this point where things are fairly clean. Rightly or wrongly, this patch will cause large amounts of pain for some portion of our userbase and I'm not sure we have enough justification to do that. That pain wouldn't likely be realised for some time either :/. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#173697): https://lists.openembedded.org/g/openembedded-core/message/173697 Mute This Topic: https://lists.openembedded.org/mt/95156228/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
