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

References	<CAE6kErhvOus7igddqKMLaJ=NdqNT9b=EUfuPVk0NAH-5U0PiNA@mail.gmail.com> <CAPTjJmqBumcD_xWLBkxP1PxgaDixqWj-+Ra8vrSO50KsyWNbxA@mail.gmail.com> <CALwzidkEUem2pEu-OP_RBV6yPZKCdQcTQZ9P86b6cPn0SVhf_Q@mail.gmail.com>
Date	2015-01-29 11:12 -0800
Subject	Re: why zip64_limit defined as 1<<31 -1?
From	jesse <chat2jesse@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.18279.1422558746.18130.python-list@python.org> (permalink)

Show all headers | 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