Python 3000: The future needs no backwards compatibility

As it is, I found myself reading an article about how python 3.0 (Also known as, and better known as, python 3000) was going to dump the backwards compatibility. Not really drastic though, because they still offer a conversion tool, and a version to switch in between (python 2.6 will take care of the later).

As I was reading the comments too, I saw that most people don’t think of it as a bad thing. Even though you’re talking about a vast amount of scripts coded in python. Many python scripts are used in linux daily, and the ever-famous zope (And the user of zope, plone, the best cms ever existed). So, this is quite the drastic decision after all.

Nonetheless, I do agree with most people saying that it is more of an improvement than a setback. Mostly examples from the java/C# world were drawn out of the closet to justify their ideas. It is common to compare python with both languages, since the include-like (Call it use, import, using, whatever) element is the same, their power is somewhat the same (Of course python is not as quick, but should not be put away for that! Speed is still good in there, especially speed of development ;) ). So comparison is about justified, and I must say that there is no reason to say why python shouldn’t change to less backwards compatibility. Java has made changes like that, and in .NET 3.5 (If I’m not wrong) C# 3.0 will have quite the less backwards compatibility too. Both offer tho usage of 2 versions in between though, making sure that your every need is filled.

However, I’m no real good python coder, I know the basics, love the language, but something in me keeps stopping me to use it. This might be solved in the new python 3.0 though. I hope so at least. In essence, python is a very good programming/scripting language.

For those wishing to know the details about python 3000 changes: http://docs.python.org/dev/3.0/whatsnew/3.0.html

Lets all wait for the newest version in a great programming language!