Why Python 4.0 won't be like Python 3.0

[Grant Edwards]

On 2014-08-19, Steven D'Aprano <steve+comp.lang.python at pearwood.info> wrote:
> 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.
>
> How was it disruptive? It was as backward compatible to 1.5 as any point
> release can be expected to be. There were syntax changes, but they added
> new syntax, and didn't take anything away.
>
> In my opinion, 2.6 was a bigger change than 2.0 from the perspective of
> backwards compatibility. 2.6 finally made raising from strings an error.

I'm probably conflating the 1.5.2/2.0 and the 2.6 stuff.  I do
remember delaying moving from 1.5.2 -> 2.0 until I really had to, but 
I don't remember why.

-- 
Grant Edwards               grant.b.edwards        Yow! Oh, I get it!!
                                  at               "The BEACH goes on", huh,
                              gmail.com            SONNY??