Python 2.7 Retirement Countdown

#1

Post by yashmehrotra » Sat, May 28, 2016, 10:24 PM UTC

Python 2.7 Retirement Countdown
pythonclock.org

Re: Python 2.7 Retirement Countdown

#2

Post by DasIch » Sat, May 28, 2016, 11:09 PM UTC

There are enough large organizations using Python that no doubt at least one will find it to be cheaper and more convenient to continue maintaining a 2.7 interpreter. Dropbox is working on one just to increase performance. PyPy also has due to how it works fundamentally a huge interest in maintaining Python 2.7 support for the forseeable future.

You've to be quite naive to believe that Python 2.7 will retire in 2020. It will only fade from popularity slightly faster.

Re: Python 2.7 Retirement Countdown

#3

Post by coldtea » Sat, May 28, 2016, 11:10 PM UTC

Yeah, don't hold your breath.

Re: Python 2.7 Retirement Countdown

#4

Post by CJefferson » Sat, May 28, 2016, 11:13 PM UTC

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.17.

Re: Python 2.7 Retirement Countdown

#5

Post by Animats » Sat, May 28, 2016, 11:15 PM UTC

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

Re: Python 2.7 Retirement Countdown

#6

Post by [deleted] » Sat, May 28, 2016, 11:16 PM UTC

[deleted]

Re: Python 2.7 Retirement Countdown

#7

Post by omash » Sat, May 28, 2016, 11:17 PM UTC

I'm hopeful we'll abandon Python 3 instead.

Re: Python 2.7 Retirement Countdown

#8

Post by Bromskloss » Sat, May 28, 2016, 11:22 PM UTC

omash wrote: post #7

I'm hopeful we'll abandon Python 3 instead.

Do you like Python 2 better than Python 3?

Re: Python 2.7 Retirement Countdown

#9

Post by afarrell » Sat, May 28, 2016, 11:22 PM UTC

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.…

How many dependencies maintained by others does your Python 2.7 code rely on?

Re: Python 2.7 Retirement Countdown

#10

Post by sandipc » Sat, May 28, 2016, 11:23 PM UTC

DasIch wrote: post #2

There are enough large organizations using Python that no doubt at least one will find it to be cheaper and more convenient to continue maintaining a 2.7 interpreter. Dropbox is working on one just to increase performance. PyPy also has due to how it works fundamentally a huge interest in maintaining Python 2.7 support for the forseeable future. You've to be quite naive to believe that Python 2.7 will retire in 2020.…

Guido van Rossum (Python BDFL) himself works for Dropbox, so I'm not sure I believe that...