Re: why zip64_limit defined as 1<<31 -1?

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!us.feeder.erje.net!feeder.erje.net!eu.feeder.erje.net!bcyclone05.am1.xlned.com!bcyclone05.am1.xlned.com!newsfeed.xs4all.nl!newsfeed3a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path	<ian.g.kelly@gmail.com>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.053
X-Spam-Evidence	'H': 0.90; 'S': 0.00; 'jesse': 0.05; 'jan': 0.12; 'archive': 0.14; 'wrote:': 0.18; 'wed,': 0.18; 'file.': 0.24; 'header:In-Reply-To:1': 0.27; 'url:bugs': 0.29; 'am,': 0.29; 'message-id:@mail.gmail.com': 0.30; 'filed': 0.31; 'url:python': 0.33; 'bugs': 0.33; 'received:google.com': 0.35; 'subject:?': 0.36; 'url:org': 0.36; 'should': 0.36; 'to:addr:python-list': 0.38; 'to:addr:python.org': 0.39; 'zip': 0.64; '2015': 0.84
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=KTnyy8FO3lDVMF13lCKQHmB07UdC146kwOEuAhJyJlI=; b=L+cLz0OENT7LRhJlT26paqWDobwarTQk8XrsBZryEKPahJHkENJ6UBm36fGsWgns0U uenDKZg9hBKspg5qkBMIKoIethTf8y+AB2LwgofrYU8yx1UIHQIgUO4k8gQLpxxQjuDx TKDLOzY3S9Sk7r8dSj9M9lJ08Zl276jDrzoRh3uGtPWOTbzMt0uPhAfn/QxKiIH+o1j0 3L9iyYN7fPm4TY48E6jqRt697eXXfHUFJb1rKtjB31FbgopdI/RGPlkBG9H3yniCFdM4 pWA5/L7KnbnYx/bIlcS9rJLeVOsQjKySa11XXjpZkVz1lacbhy1KHRGHTmCqZ4eTrm2+ AO5w==
X-Received	by 10.66.66.166 with SMTP id g6mr9438557pat.88.1422481855427; Wed, 28 Jan 2015 13:50:55 -0800 (PST)
MIME-Version	1.0
In-Reply-To	<CAE6kErhvOus7igddqKMLaJ=NdqNT9b=EUfuPVk0NAH-5U0PiNA@mail.gmail.com>
References	<CAE6kErhvOus7igddqKMLaJ=NdqNT9b=EUfuPVk0NAH-5U0PiNA@mail.gmail.com>
From	Ian Kelly <ian.g.kelly@gmail.com>
Date	Wed, 28 Jan 2015 14:50:15 -0700
Subject	Re: why zip64_limit defined as 1<<31 -1?
To	Python <python-list@python.org>
Content-Type	text/plain; charset=UTF-8
X-BeenThere	python-list@python.org
X-Mailman-Version	2.1.15
Precedence	list
List-Id	General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe	<https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive	<http://mail.python.org/pipermail/python-list/>
List-Post	<mailto:python-list@python.org>
List-Help	<mailto:python-list-request@python.org?subject=help>
List-Subscribe	<https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups	comp.lang.python
Message-ID	<mailman.18243.1422481863.18130.python-list@python.org> (permalink)
Lines	6
NNTP-Posting-Host	2001:888:2000:d::a6
X-Trace	1422481863 news.xs4all.nl 2857 [2001:888:2000:d::a6]:47847
X-Complaints-To	abuse@xs4all.nl
X-Received-Bytes	2981
X-Received-Body-CRC	2056165188
Xref	csiph.com comp.lang.python:84787

Show key headers only | View raw

On Wed, Jan 28, 2015 at 11:53 AM, jesse <chat2jesse@gmail.com> wrote:
> should not it be 1<<32 -1(4g)?
>
> normal zip archive format should be able to support 4g file.

Bugs can be filed at http://bugs.python.org/

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

Thread

Re: why zip64_limit defined as 1<<31 -1? Ian Kelly <ian.g.kelly@gmail.com> - 2015-01-28 14:50 -0700

csiph-web