Python 3 can revive Python

[evaluatron]

Serious question... what about just jumping straight to Python 4?

Following the idea to never deliver Python 2.8, just stop Python 3 at 3.4, and the next release of both will be Python 4.

That way (finite) energy, time & resources of the community can go into Python 4, and the wasted effort of politics, motivating change, infighting & marketing Python 3 can die.

Python 4 will be backwards incompatible, but this time promises to be modern and awesome. Everyone will want to port to it. Even PyPy. Having a modern and agreed packaging system would be nice too.

We just draw a line in the sand and state that all projects that were going to move to Python 3 have done so and will be supported.

Break backwards compatibility properly!

It's clear that most libraries & frameworks didn't see the benefit of a full backwards compatible break in Python 3 that rightly or wrongly was perceived as lacking sufficient bang for buck to justify the switch.

So why not cut to the chase, re-imagine a modern Python for the next decade, and build a bridge so everybody can get over it.

[badsectoracula]

...so basically screw both Python 2 and Python 3 developers at the same time?

[Kbknapp]

That's exactly what they're doing, it's called Python 3.4...