Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'versions,': 0.05; 'currently,': 0.07; 'targets': 0.07; 'terminated': 0.07; 'terry': 0.07; 'python': 0.08; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:80.91.229.12': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'received:lo.gmane.org': 0.09; 'release,': 0.09; 'wrote:': 0.15; '2to3': 0.16; '3.2,': 0.16; 'from:addr:acm.org': 0.16; 'mainstream': 0.16; 'received:198.144': 0.16; 'reedy': 0.16; 'subject:between': 0.16; '2.x': 0.19; 'etc,': 0.23; 'code': 0.24; 'libraries': 0.25; '(the': 0.28; '3.0': 0.28; 'mode': 0.28; 'far.': 0.29; 'problem': 0.29; 'version': 0.30; 'separate': 0.31; 'this.': 0.31; 'earlier': 0.32; 'received:198': 0.32; 'initial': 0.33; 'to:addr:python-list': 0.34; 'header:X-Complaints-To:1': 0.34; 'header:User-Agent:1': 0.34; 'there': 0.34; 'someone': 0.34; 'but,': 0.34; 'quite': 0.34; 'installed': 0.35; 'charset:us- ascii': 0.36; 'brief': 0.37; 'but': 0.37; 'another': 0.38; 'received:org': 0.38; 'subject:: ': 0.38; 'focused': 0.38; 'should': 0.39; 'header:Mime-Version:1': 0.39; 'unlike': 0.39; 'except': 0.39; 'to:addr:python.org': 0.39; 'introduced': 0.40; 'did': 0.40; 'target': 0.61; 'interest': 0.65; 'article': 0.76; 'easy:': 0.84; 'releases.': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Ned Deily Subject: Re: Inconsistencies between zipfile and tarfile APIs Date: Fri, 22 Jul 2011 14:17:23 -0700 References: <5fd8e664-c855-41a2-9d8b-36d4c486f0b9@n35g2000yqf.googlegroups.com> <3241cbe4-9829-438b-ac0e-a0b87aff62d9@q15g2000yqk.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: baybryj.net User-Agent: MT-NewsWatcher/3.5.3b3 (PPC Mac OS X) X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 27 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1311369463 news.xs4all.nl 23974 [2001:888:2000:d::a6]:37926 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:10155 In article , Terry Reedy wrote: > This introduced the problem that upgrading to Python 3 is no longer a > single thing. We really need 2to3.1 (the current 2to3), 2to3.2, 2to3.3, > etc, but someone would have to make the new versions, but no one, > currently, has the energy and interest to do that. So people who did not > port their 2.x code early now use the problem of multiple Python 3 > targets as another excuse not to do so now. (Actually, most 2.x code > should not be ported, but their are more libraries that we do need in 3.x.) I don't quite understand this. Since 2to3 is included with Python 3, there are, in fact, separate releases of 2to3 for each release of Python 3 so far. And, unlike with Python 2 with a large installed base across a number of versions, Python 3 version support can be and is much more focused now in its early releases. Support for 3.0 was terminated immediately upon release of 3.1. And 3.1 is now in security-fix mode only. So, except for a brief overlap after the initial release of 3.2, there has only been one Python 3 release that needs to be targeted. Of course, that will change over time as adoption continues and mainstream OS's include specific Python 3 releases. But, for now, it's easy: just target the most recent Python 3 release, currently 3.2.1. Don't worry about earlier releases. -- Ned Deily, nad@acm.org