Python 3.0, 'Python 3000', has reached its first public release. This version will be followed by beta releases throughout 2008, and the final release is scheduled for August 2008. "Python 3000 ('Py3k', and released as Python 3.0) is a new version of the language that is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed."
To read all comments associated with this story, please click here.
Member since:2005-07-06
Given that large Projects like Zope not even use the latest version of python 2, I wouldn't have too high hopes.
Backward compatibility is also very important make python a credible alternative in business.
Companies, that intend to write software with millions of lines of code are not likely to chose Phyton over e.g. java, if you need to rewrite the code every time the language developers finds a more elegant way of doing things.
In some sense I would say that the Python people are a bit too smart for their own good.
Member since:2005-11-11
You do know that they're making the "incompatible" 3.0 version in parallel with the 2.6, beackwards compatible version, right?
So for a long time, there will be a new, backwards compatible Python version as well as the 3.0
So I think they're aware that the backwards compatibility is important, while at the same time understanding that it will sometimes stand in the way of progress.
Member since:2007-09-01
Member since:2006-01-14
I was in complete agreement with you, until I read the reply to your post. I still agree with you. I think it is important that if you recognize vastly better ways to do something that you aren't so committed to compatibility that you add awkward for the sake of backward compatibility.
I think one of the things that keeps Microsoft from innovating is the legacy support they have to have. You can put me in the category of a Microsoft opponent. But, you know they have talent. If they didn't have to maintain compatibility, they could probably release something even I would like. Being open source affords the luxury of not being obligated. And, I don't think they (Guido) ever promised not to break compatibility. I don't think they are promising they will never break compatibility again, either.
Edited 2007-09-01 01:03
Member since:2006-06-21
You know, with all the money Microsoft has, I never understood why they never did what Python is doing: keep the backwards compatible stuff but also make an OS that's free of legacy and can be as good as they can make it. They probably worried it would be a competitor to Windows. Oh well, that's what you get if you value money above all else.
Member since:
2005-11-09
I respect how Python development seems to constantly be pursuing quality over maintaining backwards compatibility. An important part of optimization is being able to throw away efforts that are not suitable for the future, from a quality perspective.
I hope that the market will realize this over time, as well, and embrace the new possibilities the language seems to offer. Even if it will break existing programs.
I will *definitely* be looking into Python 3.0!