On Tue, Mar 3, 2015 at 6:39 PM, Gregory Ewing
wrote:
> Mark Lawrence wrote:
>
>> On 03/03/2015 02:29, Terry Reedy wrote:
>>
>> Plus tartfiles come from unix world, whereas zip was used instead in
>>> Windows world.
>>>
>>> Is the tart bit the thing that you can eat, a loose woman or something
>
Mark Lawrence wrote:
On 03/03/2015 02:29, Terry Reedy wrote:
Plus tartfiles come from unix world, whereas zip was used instead in
Windows world.
Is the tart bit the thing that you can eat, a loose woman or something
else, such as a typo? :)
Tartfiles would be what you get from xxx sites, no
On 03/03/2015 02:29, Terry Reedy wrote:
On 3/2/2015 8:12 PM, Ben Finney wrote:
Seth P writes:
Is there a reason tarfile and zipfile don't use the same method/member
names, where it makes sense?
The situation is known to some core developers, but is hard to change now.
One likely explanati
Seth P wrote:
Is there a reason tarfile and zipfile don't use the same method/member names,
where it makes sense?
There was talk in the python-dev mailing list recently
about creating a unified interface to the various
archiving modules. You might like to keep an eye on
what's happening there.
On 3/2/2015 8:12 PM, Ben Finney wrote:
Seth P writes:
Is there a reason tarfile and zipfile don't use the same method/member
names, where it makes sense?
The situation is known to some core developers, but is hard to change now.
One likely explanation is that the modules's APIs were design
Seth P writes:
> Is there a reason tarfile and zipfile don't use the same method/member
> names, where it makes sense?
One likely explanation is that the modules's APIs were designed by
different people unaware of the work of the other.
--
\“We have to go forth and crush every world v
Is there a reason tarfile and zipfile don't use the same method/member names,
where it makes sense? Consider the following six methods/members, which I
would expect to be the same (with the possible exception of mtime vs date_time,
which are of different types). It almost seems like someone we
