> Python 3 is the first break in backward compatibility this century!
Yep. And why is that not backward compatible too? Why don't they aim to get it right the first time? And if they don't get it right, why change it when that breaks previous uses?
I'd also remind you that we're not very far into this century yet. If that was supposed to be sarcasm, it fell short.
> Python 2.x up to 2.9 is and will be backwardly compatible with python 1.6
Then how come my Debian system needed 2.6, 2.7 _and_ 2.8 all installed at one point? Why do Pythin apps and libraries keep breaking because somebody introduced a subtle change somewhere?
Whatever Python is, it's not very robust.
I still say it's the new shiny-shiny. Nothing more.