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: Python 3 is killing Python Date: Tue, 15 Jul 2014 15:43:02 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 18 Message-ID: References: <57ajo9poljjre4c4ig0n0ss8kph8k78lp0@4ax.com> <5389cb53$0$29978$c3e8da3$5496439d@news.astraweb.com> <99b7b2a2-7521-42d7-a5a0-1a35d4d5b922@googlegroups.com> <53C4A454.9010600@gmail.com> NNTP-Posting-Host: dsl.comtrol.com X-Trace: reader1.panix.com 1405438982 4016 64.122.56.22 (15 Jul 2014 15:43:02 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Tue, 15 Jul 2014 15:43:02 +0000 (UTC) User-Agent: slrn/1.0.1 (Linux) Xref: csiph.com comp.lang.python:74491 On 2014-07-15, Kevin Walzer wrote: > I think it's more than a tempest in a teacup. > > The number of language revisions that result in deliberate, code-level > incompatibility out there is pretty small. People rightly expect that > code written for version 2.x of a language will continue to work with > version 3.x, even if 3.x is designed to go in another direction. I disagree. I don't expect backwards compatability across major version number changes. I've been doing software development for 30 years, and that has always been a pretty common rule for the projects I've worked on. -- Grant Edwards grant.b.edwards Yow! I feel partially at hydrogenated! gmail.com