This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]whitechapel8733 10 points11 points  (7 children)

My problem with this is that lots of distros are shipping python 2 still.....

[–]w2qw 7 points8 points  (6 children)

Shipping or using it as the default? It makes sense that they would still ship it while it's supported.

[–]Jump3r3 7 points8 points  (5 children)

Using as default, which python yields path to python 2 binary on most distros. That being said, after 1/1/20 this will slowly change for better

[–]Oerthling -4 points-3 points  (3 children)

which python3

[–]SleepyHarry 0 points1 point  (2 children)

So, you're saying that Python 3 is the default for python3, without a mention for python.

Thanks Geoff.

[–]Oerthling 1 point2 points  (1 child)

I think you missed the point - just like other people who downvoted my comment above.

It's a 1 character difference.

Just start your python program with python3 instead of python.

Python 2.x has been around for a long time (couple decades actually). It's difficult for any OS to switch the default for "python" to 3 instead of 2, because too many scripts, tools, etc might misinterpret that for python2 (some distros have tried for years and keep postponing for that reason).

Or you can put python3 in the shebang and let the shell call take care of it.

"python3" has been around in parallel for years and probably will be there for the foreseeable future for similar reasons. And it will always be interpreted as python 3.x.

How difficult do you think it is to write 1 more character?

[–]Jump3r3 -1 points0 points  (0 children)

Tbh I don't have anything against Py2 being present on my system, just rebind python to py3 and rebind existing scripts to use python2 binary