Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #84784
| References | <CAE6kErhvOus7igddqKMLaJ=NdqNT9b=EUfuPVk0NAH-5U0PiNA@mail.gmail.com> |
|---|---|
| Date | 2015-01-29 08:36 +1100 |
| Subject | Re: why zip64_limit defined as 1<<31 -1? |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.18240.1422481011.18130.python-list@python.org> (permalink) |
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. ChrisA
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: why zip64_limit defined as 1<<31 -1? Chris Angelico <rosuav@gmail.com> - 2015-01-29 08:36 +1100
csiph-web