@KevinH: Your rationale for making python the primary plugin language was that there exists a large body of ebook manipulation code already in python. That large body of code exists in python 2, not python 3. But anyway, I've said my piece on this subject. Choose whatever you like, time will tell whether the choice was a wise one.
As for python 2.8, I was under the impression that the SSL security backports were going to be made into 2.8, but I see that the python devs finally decided to keep it in python 2.7. So I was wrong on that. They just decided to change the meaning of patch releases to no longer mean backwards compatible releases. They are really tying themselves into knots trying to push for python 3 adoption.
|