The situation
Python 2.6 - it is really not worth the effort to support it. I mean if you start breaking your code and such, you might as well upgrade to Python 3.
The problem
Python 2.6 provides a lot of nice features over Python 2.5 ("except as" is my personal favorite). A lost of the libraries are standardized (e.g. json over simplejson) and improved in terms of performance.
However - it is not backward compatible to 2.5. The version difference of 0.1 makes it very easy to start using Python 2.6 for everything only to realize at the end that one has to regress to 2.5 for production.
The solution
Either stick with python 2.5 or stick with python 2.5.
Conclusion
It seems that in quest of progress, and by splitting their core language into three, Python community has went against one of it's core principles: "Simple is better than complex". After all if your application uses components all of which might require different versions of Python (e.g. django, apache, mysql) you suddenly find yourself in the position of the "System administrator" instead of a programmer. In this respect, even Java is easier!
Python 2.6 – an orphan child
February 11th, 2010
The current dominating version of python is 2.5. Most of the frameworks and vendors have comfortably settled on 2.5. Some of the upcoming technologies will support Python 3 exclusively. That leaves our old friend Python 2.6 out in the cold.