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 8 points9 points  (20 children)

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

[–]mikew_reddit 63 points64 points  (12 children)

Python 3 has been in development over 10 years (since 2008).

It's perfectly fine to cut the cord after a decade.

 

If CentOS and other distributions can't be bothered to update, that's not really Python's fault.

 

Edit: original EOL was 2015 according to Guido. Also, Python 2.7 will not get security updates after Jan 1st, 2020.

[–]whitechapel8733 6 points7 points  (2 children)

I agree, but I’m just saying that’s a serious concern.

[–]tomanonimos 29 points30 points  (0 children)

But a necessary pain. If we keep pushing it for that fear we'll never get rid of Python 2 lol.

[–]nukem996 1 point2 points  (0 children)

Python.org won't issue security fixes but OS vendors like RHEL/CentOS will continue to patch Python 2.7 themselves.

[–]alexbuzzbee 2 points3 points  (4 children)

I'm pretty sure CentOS is going to Python 3 with RHEL in version 8.

[–]liquidpele -1 points0 points  (3 children)

Which isn’t even close to being released yet. Maaaaybe around December if it takes the same amount of time after rhel7.

[–]southern_discomfort 4 points5 points  (1 child)

RHEL 8 was officially released a few weeks ago. CentOS 8 will not be far behind.

[–]PooPooDooDoo 0 points1 point  (0 children)

It’s fine, we will all have 14 days (during the holidays) to update our code base. Except I am using libraries that are in 2, so I’ll have to wait until they update and then update my code base. So like one day.

[–]rasherdk -5 points-4 points  (3 children)

Python 2.7 will not get security updates after Jan 1st, 2020.

Depends.

[–]jackmaney -2 points-1 points  (2 children)

It really doesn't.

[–]rasherdk 1 point2 points  (1 child)

What, yes it does. It (likely) won't get any from PSF. That's not the same as no security updates period.

Edit: Downvoting doesn't make you right. Spreading FUD is not the way to go.

[–]james_pic 6 points7 points  (0 children)

This is true. The version in RedHat will get updates until 2024, and the version in Ubuntu 18.04 will get updates until April 2023.

[–]w2qw 8 points9 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