The open source Python programming language is on the verge a sweeping revamp in the form of version 3.0 of its platform -- a release will deviate in many ways from the current, mainline Python 2.x series.

So how do you meet the needs of current 2.x Python developers while transitioning to the bleeding edge of Python 3.0 development? That's where the new Python 2.6 release comes into play.

Python 2.6 is intended to help ease the migration of Python 2.x developers to Python 3.0, a major redesign of the language that's about revisiting earlier design decisions that are now considered flaws -- and fixing them, David Goodger, an officer of the Python Software Foundation, told InternetNews.com. As yet, no date has been set for the release of Python 3.0.

The move comes as the market for Python use is expanding, thanks its use on Google's AppEngine and enterprise adoption is on the rise. Growing adoption, however, means that a growing population could be impacted with dramatic shifts in the project -- an impact that Python 2.6 aims to soften.

"Python 2.6 isn't about Python 3 compatibility, it's about Python 2.x compatibility," Goodger said. "We are not expecting or encouraging developers to migrate to Python 3 immediately, and the Python 2.x line will continue to be supported and improved for years to come. Python 2.6 is an upgrade intended for most developers of production systems. Python 3.0 is for those who like to live on the bleeding edge."

He added that design aspects of Python 2.6 pave the way for migration to Python 3.0, a release with enhancements he sees as improving the foundations of Python going forward.

Kevin Dangoor, co-author of "Rapid Web Applications with TurboGears: Using Python to Create Ajax-Powered Sites," told InternetNews.com that, in his opinion, Python 2.6 is a huge release -- probably the biggest since Python 2.2. For him, too, the key to Python 2.6 is the fact that it is a stepping stone to Python 3.0.

"In many cases, Python 2.6 lets you selectively use Python 3.0 features today, without sacrificing compatibility with existing libraries," Dangoor said. "For example, you can use the new Unicode literals or print function just with a simple import statement."