Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news.linkpendium.com!news.linkpendium.com!panix!not-for-mail
From: Grant Edwards <invalid@invalid.invalid>
Newsgroups: comp.lang.python
Subject: Re: Why Python 4.0 won't be like Python 3.0
Date: Mon, 18 Aug 2014 21:09:49 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 17
Message-ID: <lstq2t$pg5$1@reader1.panix.com>
References: <mailman.13066.1408279206.18130.python-list@python.org> <lst3t9$30d$1@reader1.panix.com> <mailman.13105.1408382076.18130.python-list@python.org>
NNTP-Posting-Host: c-24-118-110-103.hsd1.mn.comcast.net
X-Trace: reader1.panix.com 1408396189 26117 24.118.110.103 (18 Aug 2014 21:09:49 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Mon, 18 Aug 2014 21:09:49 +0000 (UTC)
User-Agent: slrn/1.0.1 (Linux)
Xref: csiph.com comp.lang.python:76514

On 2014-08-18, Ethan Furman <ethan@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.

Don't get me started on the RedHat [5678].0 OS releases from back in
the day...

-- 
Grant