3
Years
10
Months
13
Days
20
Hours
54
Minutes
31
Seconds
until a community fork occurs.
Python 2.7 Retirement Countdown
21–30 of 81 posts
Re: Python 2.7 Retirement Countdown
#22Man, the amount of people and support going for Python 2.7 is mind boggling. Coming from another language, I find the slow adoption of Python 3 insane. Don't you want Python as a language to advance?
Python should've abandoned and deprecated 2 ages ago. I still see new tutorials teaching 2. What the hell.
Re: Python 2.7 Retirement Countdown
#23I'm hopeful we'll abandon Python 3 instead.
Could you elaborate on that?
Re: Python 2.7 Retirement Countdown
#24Man, the amount of people and support going for Python 2.7 is mind boggling. Coming from another language, I find the slow adoption of Python 3 insane. Don't you want Python as a language to advance? Python should've abandoned and deprecated 2 ages ago. I still see new tutorials teaching 2. What the hell.
[deleted]
Re: Python 2.7 Retirement Countdown
#25The amount of effort Python puts into screwing 2.x users is excessive.
Yes! How dare they not support a six-year-old version of the language for more than ten years!
Re: Python 2.7 Retirement Countdown
#263 Years 10 Months 13 Days 20 Hours 54 Minutes 31 Seconds until a community fork occurs.
I was going to say the same comment.
Re: Python 2.7 Retirement Countdown
#27No, 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.…
Your C code might still work but are you not relying on any libraries which might have been updated in 15 years in a non-backwards compatible way and thus broken your build?
Re: Python 2.7 Retirement Countdown
#28331/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.
The tool they use to determine py3 support is the following: https://github.com/brettcannon/caniusepython3
They have overridden mysql-python with mysqlclient https://github.com/PyMySQL/mysqlclient-python
Re: Python 2.7 Retirement Countdown
#29The 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.
And vice-versa, it is not like users have some grunt against developers. They just don't want to go through the pain of having to migrate their applications and the instability that this will bring.
(Disclaimer: I am not supporting any side)
Re: Python 2.7 Retirement Countdown
#30No, 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.…
My python code from 2000 will be supported until 2020, so I'm not sure which language you refer to when you say it'll "break within a year".