The first thing would be to direct the "python" command to running Python 3, and the second would be to not have Python 2 pre-installed.
It is and Raspbian/RPD has already moved the Desktop over to Python3 and have anything python(2) as hard to get as as possible.
This is what Ubuntu does! https://twitter.com/ben_nuttall/status/ ... 5200169989paddyg wrote: Maybe what's needed is an LXTermial hack (that can be switched off by accomplished users) that spots when a new user is typing pip or python and pops up a helpful suggestion. It could even have an animated paperclip or such-like.
The EOL was supposed to be 2015, but support was extended by five years. People have had *plenty* of notice.hippy wrote: It would IMO also be desirable if Python2 were still installable, and any apt-get Python 2 packages remained available for some time after.
I'm curious. What is it about Python3 that you dislike so much? As far as I can tell the differences between 2 and 3 are not big and not much needs changing to get your old code running with 3.I'm not moving to Python3 as I dislike it.
Let's hope you are not doing anything serious in Python that requires security.I'll stick with my perfectly functional Python2
That is absurd.Sounds like something Microsoft would pull.
If Ubuntu does this why can't Raspbian? Canonical is less 'beginner programmer' oriented than the Raspberry Pi Foundation, after all. There still seems to be constant stream of people asking for help on this forum because they have unwittingly used python. And that turned out to be different from what they intended.paddyg wrote:
Maybe what's needed is an LXTermial hack (that can be switched off by accomplished users) that spots when a new user is typing pip or python and pops up a helpful suggestion. It could even have an animated paperclip or such-like.
This is what Ubuntu does! https://twitter.com/ben_nuttall/status/ ... 5200169989
Distributors may choose to set the behavior of the python command as follows:
not provide python command,
allow python to be configurable by an end user or a system administrator.
Debian releases are every 2 years, and Python 2.7 was still in life when Buster was released. It's not going to be dropped from Buster mid-life. Come the next Debian release (Bullseye), Python 2 will be dropped from the image, and I imagine Debian will do something with the "python" command as I said Ubuntu have done.
Raspbian is pretty much a straight recompilation of Debian Stable (currently Buster), with a load of Pi specific bits added.
Both Ubuntu and Raspbian are derivatives of Debian, but the similarity basically ends there.
That sounds like it could be a major concern but likely isn't. Python 3 users already have to specify "python3" so this change won't affect them, and that should be the majority of Python users on a Pi these days. Those still using 2.7 will have to get used to specifying "python2", which they should have transitioned to doing anyway, or create the symlink themselves.
Code: Select all
#!/usr/bin/python3 #!/usr/bin/python2 print("This is Python 3 and Python 2 compatible")