Why Python 4.0 won't be like Python 3.0

[Emile van Sebille]

On 8/18/2014 2:09 PM, Grant Edwards wrote:
> On 2014-08-18, Ethan Furman <ethan at stoneleaf.us> wrote:
>> 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.
>
> So was 2.0, only it wasn't quite as distruptive as 3.0.

As I recall, 2.0 _was_ 1.6.

Emile