Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #10155

Re: Inconsistencies between zipfile and tarfile APIs

From Ned Deily <nad@acm.org>
Subject Re: Inconsistencies between zipfile and tarfile APIs
Date 2011-07-22 14:17 -0700
References (1 earlier) <mailman.1344.1311308080.1164.python-list@python.org> <3241cbe4-9829-438b-ac0e-a0b87aff62d9@q15g2000yqk.googlegroups.com> <mailman.1347.1311313569.1164.python-list@python.org> <dc3861c9-cd36-4a42-b020-b3b008b85225@12g2000yqr.googlegroups.com> <j0cjaf$mum$1@dough.gmane.org>
Newsgroups comp.lang.python
Message-ID <mailman.1392.1311369463.1164.python-list@python.org> (permalink)

Show all headers | View raw


In article <j0cjaf$mum$1@dough.gmane.org>,
 Terry Reedy <tjreedy@udel.edu> 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

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PyWart 1001] Inconsistencies between zipfile and tarfile APIs rantingrick <rantingrick@gmail.com> - 2011-07-21 20:46 -0700
  Re: [PyWart 1001] Inconsistencies between zipfile and tarfile APIs Corey Richardson <kb1pkl@aim.com> - 2011-07-22 00:13 -0400
    Re: Inconsistencies between zipfile and tarfile APIs rantingrick <rantingrick@gmail.com> - 2011-07-21 21:48 -0700
      Re: Inconsistencies between zipfile and tarfile APIs Corey Richardson <kb1pkl@aim.com> - 2011-07-22 01:05 -0400
        Re: Inconsistencies between zipfile and tarfile APIs rantingrick <rantingrick@gmail.com> - 2011-07-21 22:58 -0700
          Re: Inconsistencies between zipfile and tarfile APIs Lars Gustäbel <lars@gustaebel.de> - 2011-07-22 10:49 +0200
            Re: Inconsistencies between zipfile and tarfile APIs rantingrick <rantingrick@gmail.com> - 2011-07-22 10:38 -0700
      Re: Inconsistencies between zipfile and tarfile APIs Terry Reedy <tjreedy@udel.edu> - 2011-07-22 01:45 -0400
        Re: Inconsistencies between zipfile and tarfile APIs rantingrick <rantingrick@gmail.com> - 2011-07-21 23:40 -0700
          Re: Inconsistencies between zipfile and tarfile APIs Corey Richardson <kb1pkl@aim.com> - 2011-07-22 03:19 -0400
          Re: Inconsistencies between zipfile and tarfile APIs Terry Reedy <tjreedy@udel.edu> - 2011-07-22 15:33 -0400
          Re: Inconsistencies between zipfile and tarfile APIs Ned Deily <nad@acm.org> - 2011-07-22 14:17 -0700
          Re: Inconsistencies between zipfile and tarfile APIs Terry Reedy <tjreedy@udel.edu> - 2011-07-22 20:31 -0400
      Re: Inconsistencies between zipfile and tarfile APIs Ryan Kelly <ryan@rfk.id.au> - 2011-07-22 15:56 +1000
  Re: [PyWart 1001] Inconsistencies between zipfile and tarfile APIs Lars Gustäbel <lars@gustaebel.de> - 2011-07-22 10:26 +0200
    Re: Inconsistencies between zipfile and tarfile APIs rantingrick <rantingrick@gmail.com> - 2011-07-22 10:11 -0700
      Re: Inconsistencies between zipfile and tarfile APIs Chris Angelico <rosuav@gmail.com> - 2011-07-23 03:23 +1000
      Re: Inconsistencies between zipfile and tarfile APIs Chris Angelico <rosuav@gmail.com> - 2011-07-23 03:25 +1000
  Re: [PyWart 1001] Inconsistencies between zipfile and tarfile APIs Thomas Jollans <t@jollybox.de> - 2011-07-22 12:31 +0200
  Re: [PyWart 1001] Inconsistencies between zipfile and tarfile APIs Tim Chase <python.list@tim.thechases.com> - 2011-07-22 06:25 -0500
  Re: [PyWart 1001] Inconsistencies between zipfile and tarfile APIs Terry Reedy <tjreedy@udel.edu> - 2011-07-22 15:49 -0400

csiph-web