3 ms·
How is 2.x dead? Everyone in the Python community is using and developing for 2.x. If you develop for Py3k, then you loose backward compatibility and you can't
by amix 17y ago
How is 2.x dead? Everyone in the Python community is using and developing for 2.x. If you develop for Py3k, then you loose backward compatibility and you can't use upcoming optimizations like Unladen Swallow.
I think Python might end up in a situation like PHP4 and PHP5 - where tons of people still use PHP4, even if PHP5 holds tons of improvements and is around 5 years old.
Breaking backward compatibility to fix some essential things is an ok move, but I think it's only going to work if Python3k has a much better offering than it currently has.
- scott_s 17y agoIt's not a language, but look at the Linux kernel. The jump from 2.4 to 2.6 was significant - programs that took advantage of some of the added support in 2.6 couldn't run on 2.4 kernels. 2.4 was maintained because many people used it, but eventually all new development started occurring in 2.6 Now 2.6 is the default. I hope Python will go through the same process. It's not that Python 2.x is dead, but that we've scheduled its retirement.
- masklinn 17y ago> programs that took advantage of some of the added support in 2.6 couldn't run on 2.4 kernels. yeah but programs which ran on 2.4 kernels still run on 2.6 right? So the situation is totally different.
- scott_s 17y ago"Totally different," no. Not exactly the same, yes. Similar enough to make a meaningful comparison? I think so.
- jerf 17y ago"How is 2.x dead?" It's dead in that precious "The technorati are planning on moving away from it in the next couple of years" sense, which has, like, virtually no relevance to anything else. See also: Windows (and Microsoft in general), iPhone App Store, and Twitter. All dead, baby, dead as a doornail.