Why Python 4.0 won't be like Python 3.0

[Ethan Furman]

On 08/18/2014 07:51 AM, Grant Edwards 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.

Even our own 3.0 was like that.


> I don't think one (or several) blog posts is going to change the
> perceptions and expectations that have been coditioned into us by
> decades of experience with x.0 versions of countless software
> packages. If it's just another in a a series of incremental "bug fix
> and minor enhancements without breaking backwards incompatibility"
> releases, you simply do not call it vers x.0.

Yup.

--
~Ethan~