I am not convinced there have been that many problems. I don't see the proposed change making things any worse, only improving things.
At present the only reported issue should be Python 3 novices with "I type "python" and it won't run my Python 3 code". The answer is "You must type python3, make sure your codebase shebangs specify python3".
Code: Select all
Current Stop-gap Long term "python" -> 2 "python" -> ? "python" -> 3 "python2" -> 2 "python2" -> 2 "python2" -> 2 "python3" -> 3 "python3" -> 3 "python3" -> 3
During the stop-gap period it does depend how that stop-gap is implemented. But the answer for Python 3 users is probably the same, and for Python 2 users it will likely be "Python 2 is deprecated, get used to typing "python2", update your codebase shebangs, or move to using Python 3".
Long term it will be any lingering Python 2 users complaining "I type "python" and it won't run my Python 2 code". The answer becomes "You need to install Python 2 and then type "python2", update your codebase shebangs, or move to using Python 3".
So Python 3 users shouldn't be any worse off, and long term shouldn't have any issues, no matter what they are typing.
Python 2 users will become the ones with problems but they should be declining in number as time goes on.
A global issue arises when some systems have moved to "python" defaulting to 3 while others still default to 2. There's not much anyone can do about that but it's no worse than most systems having moved to systemd while some haven't.
If Raspbian is tracking Debian then it will be those other system's problem if typing "python" doesn't launch Python 3, not Raspbian's.