Why Python 4.0 won't be like Python 3.0

[ElChino]

"Grant Edwards" <invalid at invalid.invalid> wrote:

> To all of us out here in user-land a change in the first value in the
> version tuple means breakage and incompatibilities. And when the
> second value is "0", you avoid it until some other sucker has found
> the bugs and a few more minor releases have come out.

"Three shall be the number thou shalt count, and the number of the 
counting shall be three, no more, no less. .."
  https://www.youtube.com/watch?v=xOrgLj9lOwk   (1:30)

Or lets make the version asymptotically grow towards 4.
Any sensible function for that?

--gv