2020-07-13, Bruce Richardson: > In the absense of a "proper" solution, is the simplest option to > change the shebangs to all be python3, but leave the python2 > compatibility in place, and add the warnings for anyone running it > explicitly using python2?
Personally, I am OK with this solution. However, this is quite radical. I guess we would need to make it obvious to everyone using 20.08 that all Python scripts will now use python3 unless they explicitly replace the shebangs when installing them. I wonder if that would not be better to add a build option to force these shebangs. -- Robin
