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

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.stack.nl!newsfeed.xs4all.nl!newsfeed3a.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path	<chat2jesse@gmail.com>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.010
X-Spam-Evidence	'H': 0.98; 'S': 0.00; 'jesse': 0.05; '32-bit': 0.09; 'indicates': 0.09; 'cc:addr:python-list': 0.11; 'bug': 0.12; 'jan': 0.12; 'archive': 0.14; '>>': 0.16; 'integer.': 0.16; 'reason?': 0.16; 'unsigned': 0.16; 'wrote:': 0.18; 'wed,': 0.18; 'thu,': 0.19; 'email addr:gmail.com>': 0.22; 'cc:addr:python.org': 0.22; 'integer': 0.24; 'file.': 0.24; 'cc:2**0': 0.24; '>': 0.26; 'signed': 0.27; 'header:In-Reply- To:1': 0.27; 'chris': 0.29; 'url:bugs': 0.29; 'am,': 0.29; 'message-id:@mail.gmail.com': 0.30; 'url:mailman': 0.30; 'boundary': 0.31; 'file': 0.32; 'url:python': 0.33; 'limitation': 0.33; 'received:google.com': 0.35; 'url:listinfo': 0.36; 'thanks': 0.36; 'subject:?': 0.36; 'url:org': 0.36; 'should': 0.36; 'problems': 0.38; 'pm,': 0.38; 'does': 0.39; 'url:mail': 0.40; 'even': 0.60; 'simply': 0.61; 'zip': 0.64; 'to:addr:gmail.com': 0.65; 'details': 0.65; 'limit': 0.70; '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:date:message-id:subject:from:to :cc:content-type; bh=/OPkMSOeuOp1pb2/Bd8c8sBpe2V9UOiGZL+JFIglxGk=; b=B1/+T6ZhTokokVEak+doI6Jno3ANX3ThCNU84hyP6gcwR8i4+2p0ujoQ++yIAhXOPz R6GQYIvKhcZL1+lbxAf40wX1URy6ffoR5HlZslVh4QkDq6VXKXhn5B+7T9xOA9waG2zB iNKQaFcLa1+CE5tWb1kJ6oByowSrUfWKx0Uvy8UQhRW3+sCyKtRZf0PZK3L4ta3ZdSUi KwmHGSw4AQGf3YrWiz/eYQ3fAp2UfEpnSqwKbUamy2ybUPaLsALxcVd450BZ3b/c6Syg q8TuLhWTyYbBiO465bLzDFYJaiFR+TL0SmoSBc+NOl4NpCzNwulrSe+UmsLeypkwRuf0 35Dg==
MIME-Version	1.0
X-Received	by 10.194.94.164 with SMTP id dd4mr4493639wjb.56.1422558743750; Thu, 29 Jan 2015 11:12:23 -0800 (PST)
In-Reply-To	<CALwzidkEUem2pEu-OP_RBV6yPZKCdQcTQZ9P86b6cPn0SVhf_Q@mail.gmail.com>
References	<CAE6kErhvOus7igddqKMLaJ=NdqNT9b=EUfuPVk0NAH-5U0PiNA@mail.gmail.com> <CAPTjJmqBumcD_xWLBkxP1PxgaDixqWj-+Ra8vrSO50KsyWNbxA@mail.gmail.com> <CALwzidkEUem2pEu-OP_RBV6yPZKCdQcTQZ9P86b6cPn0SVhf_Q@mail.gmail.com>
Date	Thu, 29 Jan 2015 11:12:23 -0800
Subject	Re: why zip64_limit defined as 1<<31 -1?
From	jesse <chat2jesse@gmail.com>
To	Ian Kelly <ian.g.kelly@gmail.com>
Content-Type	multipart/alternative; boundary=047d7bb0410297ef4e050dcf4486
Cc	Python <python-list@python.org>
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.18279.1422558746.18130.python-list@python.org> (permalink)
Lines	75
NNTP-Posting-Host	2001:888:2000:d::a6
X-Trace	1422558746 news.xs4all.nl 2954 [2001:888:2000:d::a6]:44612
X-Complaints-To	abuse@xs4all.nl
Xref	csiph.com comp.lang.python:84839

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On Jan 29, 2015 9:27 AM, "Ian Kelly" <ian.g.kelly@gmail.com> wrote:
>
> On Wed, Jan 28, 2015 at 2:36 PM, Chris Angelico <rosuav@gmail.com> wrote:
> > On Thu, Jan 29, 2015 at 5: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.
> >>
> >> thanks
> >
> > 1<<31-1 is the limit for a signed 32-bit integer. You'd have to look
> > into the details of the zip file format to see whether that's the
> > official limit or not; it might simply be that some (un)archivers have
> > problems with >2GB files, even if the official stance is that it's
> > unsigned.
>
> The bug in which zip64 support was added indicates that the value was
> indeed chosen as the limit of a signed 32-bit integer:
>
> http://bugs.python.org/issue1446489

ok,  then why signed 32-bit integer instead of unsigned 32 integer? any
technical limitation reason? the chosen 2G boundary does not conform to zip
standard specification.

> --
> https://mail.python.org/mailman/listinfo/python-list

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

Thread

Re: why zip64_limit defined as 1<<31 -1? jesse <chat2jesse@gmail.com> - 2015-01-29 11:12 -0800

csiph-web