Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
comp.lang.python
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Python 3000: Standard API for archives?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Tim Golden  
View profile  
 More options Jun 5 2007, 12:55 am
Newsgroups: comp.lang.python
From: Tim Golden <m...@timgolden.me.uk>
Date: Mon, 04 Jun 2007 15:55:30 +0100
Local: Tues, Jun 5 2007 12:55 am
Subject: Re: Python 3000: Standard API for archives?
Reply to author | Forward | Print | View thread | Show original | Report this message | Find messages by this author

Chuck Rhode wrote:
> samwyse wrote this on Mon, 04 Jun 2007 12:02:03 +0000.  My reply is
> below.

>> I think it would be a good thing if a standardized interface
>> existed, similar to PEP 247.  This would make it easier for one
>> script to access multiple types of archives, such as RAR, 7-Zip,
>> ISO, etc.

> Gee, it would be great to be able to open an archive member for update
> I/O.  This is kind of hard to do now.  If it were possible, though, it
> would obscure the difference between file directories and archives,
> which would be kind of neat.  Furthermore, you could navigate archives
> of archives (zips of tars and other abominations).

FWIW, there's no need to get hung on Python-3000 or
any other release. Just put something together a module
called "archive" or whatever, which exposes the kind of
API you're thinking of, offering support across zip, bz2
and whatever else you want. Put it up on the Cheeseshop,
announce it on c.l.py.ann and anywhere else which seems
apt. See if it gains traction. Take it from there.

NB This has the advantage that you can start small, say
with zip and bz2 support and maybe see if you get
contributions for less common formats, even via 3rd
party libs. If you were to try to get it into the stdlib
it would need to be much more fully specified up front,
I suspect.

TJG


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google