Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Python 2.7 Retirement Countdown

pythonclock.org

Post reply on HN
Print view View original

11–20 of 81 posts

Re: Python 2.7 Retirement Countdown

#11

Post by afarrell »

Animats wrote: post #5

The amount of effort Python puts into screwing 2.x users is excessive.

It's not that maintainers want to screw anyone over, it's that folks who give away labor for free to maintain libraries want to be able to use the new features in 3.x without spending additional unpaid labor to maintain separate 2.x versions.

Re: Python 2.7 Retirement Countdown

#12

Post by ieverdream »

CJefferson wrote: post #4

No, I'm getting sick of my code being broken. My C code from 15 years ago works fine, but code in other languages can end up breaking within a year. I've moved much of my development back to C++ just so I can have reasonable confidence my code will work when I come back to it in a couple of years. I don't care if Python 2.7 never gains another feature, as long as my code will still work in Windows 13 and Mac OS X 10.…

right tool for right job :). You use python for specific purpose, if the Python won't be maintained anymore, you can keep the current compiler, so it doesn't matter.

Re: Python 2.7 Retirement Countdown

#13

Post by jgalt212 »

Most everything good from Python 3 has been back-ported to 2.7. Except for built in parameterized tests in unittest.

Python 3 has the subTest context manager (which looks great)

https://docs.python.org/3/library/unittest.html#distinguishi...

In 2.7 you must use pytest, ddt, nose-paramemterized or dynamically add test methods to a TestCase class at runtime.

Re: Python 2.7 Retirement Countdown

#14

Post by Retra »

Animats wrote: post #5

The amount of effort Python puts into screwing 2.x users is excessive.

Are you talking about all the effort put into back-porting Python 3 features into Python 2? Or all the random threads attacking Python 3 developers for their unpaid efforts and initiative in making the language better? Or maybe you're referring to the 2020 deadline, which is tortuously long?

Re: Python 2.7 Retirement Countdown

#17

Post by dkarapetyan »

This again? Python 2.7 is never going away, no matter how much people wish it did. Python is the Cobol/Java of dynamic languages. There is way too much volume of code written in it. This means there is a golden consulting opportunity for those willing to take it: support 2.7 code/libraries for money.

Re: Python 2.7 Retirement Countdown

#19

Post by kinkdr »

Grokzen wrote: post #15

331/360 of the most popular repos on pypi supports py3 http://py3readiness.org/ . Also python 3 support is increasing, while python 2 support is decreasing overall https://blogs.msdn.microsoft.com/pythonengineering/2016/03/0...

Is the list correct?

It shows MySQL-python as 3.0 ready, but MySQL-python page (https://pypi.python.org/pypi/MySQL-python/1.2.5) notes:

> MySQL-3.23 through 5.5 and Python-2.4 through 2.7 are currently supported. Python-3.0 will be supported in a future release. PyPy is supported.

Re: Python 2.7 Retirement Countdown

#20

Post by StavrosK »

dkarapetyan wrote: post #17

This again? Python 2.7 is never going away, no matter how much people wish it did. Python is the Cobol/Java of dynamic languages. There is way too much volume of code written in it. This means there is a golden consulting opportunity for those willing to take it: support 2.7 code/libraries for money.

This again indeed, because Python 2.7 is going away. Python 3 is the future, and we've been resting on our "eh, python 2.7 is convenient enough" mindset for too long. We should just bite the bullet and move to 3, which isn't even that bad of a migration.

Also, "supporting legacy code for money" is already everyone's job, unless you're implying that there are as many Python programmers as there are COBOL ones.

Post reply on HN