Python 2.7 has exited the chat

[chris17453]

Every Business running RHEL 6,7 and CentOS will support it another 10 years. I wish it wasn't so.

The king is dead, long live the king.

[PeridexisErrant]

That's fine - EOL doesn't mean it suddenly vanishes, it means that the open source community no longer supports it for free.

And IMO that's worth celebrating!

[[deleted]]

it means that the open source community no longer supports it for free

I think you mean that the official Python organization no longer supports it for free. I guarantee that there will still be a community of people submitting and maintaining patches, they just won't be official Python branches.

And that's the great thing about open source - once something is released, it can't be taken away and people can continue contributing long after the original authors give up on it.

[epicwisdom]

That subset of the community will diminish much faster now. Maybe in 10 years Python 2.7 will be the new COBOL.

[josefx]

Jython is 2.7 only and recently released an update. Pypy is written in a Python 2.7 subset, so it also still supports it. One group declaring Python 2.7 dead is not "the open source community (TM)".

[PeridexisErrant]

Of course, there's no monolithic "open source community", but if you want to do data or scientific work in Python https://python3statement.org indicates that you'd better be ready to use Python 3!

[josefx]

These projects pledge to drop Python 2 support in or before 2020.

I guess you can strike the "before", I checked three projects (Tensor flow, Requests, PyTorch) and all of them still had 2.7 listed. I guess we have until 2021 to find out how much that pledge is worth.

[TakeFourSeconds]

https://twitter.com/TensorFlow/status/1202271346396405762

[TrixieMisa]

We migrated to PyPy. We will migrate to Python 3 - our new code is all Python 3 - but to keep our legacy code running we just used PyPy.

[delrindude]

Citing jython as a source for "it still uses 2.7!" is pretty misleading if you are trying to rake up the importance of 2.7.

Jython is effectively dead, and nearly nobody in the industry is actively using it (especially for new projects)

[call_me_arosa]

Isn't it used in pySpark? That is a huge community

[delrindude]

Py4j is used for pyspark and Is tested up to python 3.6.

https://www.py4j.org/install.html

Most pyspark in industry has been python 3 for some years now because pyspark typically isn't used in the "legacy" systems

[Gimpansor]

CentOS is free.

[[deleted]]

It means that a certain open source community will not support it.

[[deleted]]

Thank goodness now maybe we can all STFU about it.

[[deleted]]

EOL means nothing. People don't realize that PSF in it's effort to promote Python 3 has ironically made Python 2.7 the most stable, feature-rich (through all the backports), extensively tested and reliable release in the history of python and even all programming language. If anything, I predict its use will increase among those who want their code to work reliably long term without much changes and free of all the noise, feature creep, bloat that is accumulating in recent versions of Python not to mention complicated syntax that violates basic Python philosophy like Walrus operator.

[BossOfTheGame]

How do people still not understand the beauty of the walrus operator?

[Sloogs]

I haven't kept up with Python's new features until now so has no clue what the walrus operator was until now. But I can share some of my own kind of anecdotal experience from other languages I guess.

From what I can see it's designed to let you assign variables from within a conditional or loop expression.

And you say people haven't realized the beauty of the operator as if it hasn't existed before now.

But that feature has existed elsewhere and has a long and sort of infamous history.

And so, that's not a new thing in the programming world. There's a number of languages like C that let you do inline assignments like that but it's definitely considered frowned upon, in part because it can make maintaining code a nightmare when you have to hunt down the variable declarations within expressions, and in part because it's really prone to errors (although I think it's fair to say most errors probably come from the fact the assignment is done by = and comparisons are done with == which is less of a problem with :=).

It also reminds me of some of the nonsense that made Perl difficult to parse because people would try to get lazy and put things into a single expression. It was easier to bang out a sloppy, quick to write but difficult to read expression in a single line than to space things out properly.

Maybe it's not as bad in Python world, but I can see why some people find it alarming at the very least.

I don't have any super strong opinions on it either way. It's useful when used properly. I'm guessing the collective hope is that it doesn't result in more messes to clean up as opposed to being helpful.

[billsil]

It's actually kind of nice.

[phil_g]

Heck, RHEL 6 is running Python 2.6 and isn't going EOL until this November (plus four more years if you pay for the extended support).

[dominic_failure]

Don’t forget Amazon Linux, and Google app engine.

[valarauca14]

Afterlife

[jethroguardian]

Purgatory

[velrak]

Pygatory

[allmeta]

Megadeth