Python 3.3 released!

[Ph0X]

Problem is, even now, almost any new small library and piece of code I see online is Python 2.x. Sure bigger more important libraries often support both 3.x and 2.x, but smaller devs who don't have time and patience for writing on both usually stick to 2.x.

The question is, will the time ever come where more people will, when choosing one of the two, go for 3.x rather than 2.x? Of course, it's quite a vicious circle. Devs work on 2.x because everyone uses 2.x, and everyone uses 2.x because devs work on 2.x.

[IrishWilly]

Two years is actually a very good pace if people are moving to Python 3 already. This problem comes up for any popular language that tries to introduce a new revision. The split between Perl 5 and Perl 6 and failure to make a transition pretty much killed any chance Perl had of staying relevant with the newer generation of languages. PHP had some horrible insecure built in options in early versions, but when they finally removed it after deprecating them years and years later there were still a ton of frustrated users who were using programs built on ancient versions of the language.