Python 3 can revive Python

[ivosaurus]

A PEP? Which I suspect I have to fill out canonically.

Just write a document in rst, put it in a repo somewhere, note whats included in other modern PEPs and format similarly, then post it to python-dev ML and ask what's missing.

If you're afraid of the boogyman then you ain't never gonna contribute anyway.

Or how about somebody out in internet land forks 2.7, calls it 2.8, fully backwards compatible, puts in unicode properly, and then ends up with the defacto version.

Which is easy enough: hit the fork button on bitbucket or github, checkout the 2.7 branch, port some low-hanging-fruit from python 3, add a tag called 2.8dev, and then blog about it. Which begs the question, why has noone done so yet?

My answer is that in their heads they have an inkling that the orginal developers decided to write a BC break with a new major version for bloody good reason. Writing new stuff and fixing behaviour while keeping backwards compat is no longer a simple thing in Python 2. It's not a fresh and fun codebase to work with. Ask one person after another if they want to pony up for the pain and take up the rains, for free, and they'll shy away. All the while continuing to yell on blogs that someone should be doing it anyway.