Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: Why Python 4.0 won't be like Python 3.0 Date: Tue, 19 Aug 2014 14:27:35 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 30 Message-ID: References: <53f29983$0$29986$c3e8da3$5496439d@news.astraweb.com> NNTP-Posting-Host: dsl.comtrol.com X-Trace: reader1.panix.com 1408458455 10796 64.122.56.22 (19 Aug 2014 14:27:35 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Tue, 19 Aug 2014 14:27:35 +0000 (UTC) User-Agent: slrn/1.0.1 (Linux) Xref: csiph.com comp.lang.python:76568 On 2014-08-19, Steven D'Aprano wrote: > Grant Edwards wrote: > >> On 2014-08-18, Ethan Furman 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??