On Wed, 23 Nov 2022 at 10:59, Ross Burton <ross.bur...@arm.com> 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. > > But as per PEP 0384, /usr/bin/python could be python2, or not there at all. > Software should use python3.
But would anyone pay attention to the PEP when writing new scripts? If /usr/bin/python is available by default, as it is already on Fedora, and probably will be on Debian (in testing/sid there is no choice between 2 and 3 anymore - 2 is gone, and that clears the road to have python->python3 installed by default), then it's not unreasonable to have the script use that. I wouldn't want to know or care about python's historical baggage. That's why I'm saying we're going to see more upstreams that are just having #!/usr/bin/python and don't give a damn, even when you point it out to them. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#173712): https://lists.openembedded.org/g/openembedded-core/message/173712 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] -=-=-=-=-=-=-=-=-=-=-=-
