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
Date: Fri, 22 Jul 2011 10:49:15 +0200
From: Lars =?iso-8859-1?Q?Gust=E4bel?= <lars@gustaebel.de>
To: rantingrick <rantingrick@gmail.com>
Subject: Re: Inconsistencies between zipfile and tarfile APIs
Mail-Followup-To: Lars =?iso-8859-1?Q?Gust=E4bel?= <lars@gustaebel.de>, rantingrick <rantingrick@gmail.com>, python-list@python.org
References: <5fd8e664-c855-41a2-9d8b-36d4c486f0b9@n35g2000yqf.googlegroups.com> <mailman.1344.1311308080.1164.python-list@python.org> <3241cbe4-9829-438b-ac0e-a0b87aff62d9@q15g2000yqk.googlegroups.com> <mailman.1346.1311311483.1164.python-list@python.org> <96257847-f17d-4681-9b71-b353c76c86fe@s17g2000yqs.googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <96257847-f17d-4681-9b71-b353c76c86fe@s17g2000yqs.googlegroups.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: python-list@python.org
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.1355.1311324559.1164.python-list@python.org>
Lines: 55
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:10088

On Thu, Jul 21, 2011 at 10:58:37PM -0700, rantingrick wrote:
> My hat is off to you Mr. Richardson. I've even considered creating my
> own clean versions of these two modules, because heck, it is not that
> difficult to do! However we must stop fixing these warts on a local
> level Corey. We MUST clean up this damn python stdlib once and for
> all.

One could get the impression that you are leading a grass-roots movement
fighting a big faceless corporation. Instead, what you're dealing with is this
warm and friendly Python community you could as well be a part of if you are a
reasonable guy and write good code.

> I am willing and you are willing; that's two people. However, can we
> convince the powers that be to upgrade these modules? Sure, if we get
> enough people shouting for it to happen they will notice. So come on
> people make your voices heard. Chime in and let the devs know we are
> ready to unite and tackle these problems in our stdlib.

Yeah, great. Please write code. Or a PEP.

> What this community needs (first and foremost) is some positive
> attitudes. If you don't want to write the code fine. But at least
> chime in and say... "Hey guys, that's a good idea! I would like to see
> some of these APIs cleaned up too. good luck! +1"

+1

> Now, even if we get one hundred people chanting... "Yes, Yes, Fix This
> Mess!"... i know Guido and company are going to frown because of
> backwards incompatibility. But let me tell you something people, the
> longer we put off these changes the more painful they are going to
> be.

And backwards compatibility is bad why? Tell me, what exactly is your view
towards this? Should there be none?

> Python 3000 would have been the perfect time to introduce a more
> intuitive and unified zip/tar archive module however that did not
> happen. So now we need to think about adding a duplicate module
> "archive.py" and deprecating zipfile.py and tarfile.py. We can remove
> the old modules when Python 4000 rolls out.
> 
> That's just step one people, we have a long way to go!

archive.py is no new idea. Unfortunately, to this day, nobody had the time to
come up with an implementation.

Let me say it again: less false pathos, more code. Please.

-- 
Lars Gustäbel
lars@gustaebel.de

To a man with a hammer, everything looks like a nail.
(Mark Twain)