that's why virtualenv was invented
Yes and shouldn't it also be the OSes that use it to isolate their default Python install?If you require 2.7 or 3.x goodness, you can always set-up different environments separate from the OS's Python and just be happy with it.
And, BTW, I never put boneheaded in quotes ;-)
Any system scripts that require 2.4 can then change their shebang to say /usr/bin/python2.4. At the very same time, packages for newer pythons can be made available for ease-of-use for the rest of the world. This breaks nothing.
Also, this is how things improve. Someone doesn't like the current state of affairs and changes it.
What specific Python dependency did the move to C cure? What are the most common complains regarding libraries and versions? Perhaps listing them can help change whatever is wrong.
An end-user of an application doesn't want to fiddle around with library management tools.
It's a shame he felt he had to tear out Python. I understand the pain of relying on distro-supported Python. You basically have to target 2.3 at minimum if you want to distribute an application. If you have windows users, it can be even more painful.
Theoretically, couldn't you have configure check your setup for Python 2.x? Setup your make process to download and install the proper python in a local build environment? I'm just running off random ideas, not sure if it would be feasible.
Too late for Mongrel2 of course, but C isn't so bad either.
I too am frustrated by ancient versions of server OSs that use equally ancient versions of Python, but that's why virtualenv was invented. And source distributions. I am happy using it when required.
Being "stable" in OS terms is not changing APIs very often. One of the good things is that I know that code I wrote for RHEL 4 the day it was launched will run flawlessly on RHEL 4 today. The primary goal of such a Linux distro is that "it has to work". I won't touch the system parts.