Re: zipfile 2GB problems?
- From: xamdam <maxkhesin@xxxxxxxxx>
- Date: Mon, 16 Jul 2007 18:59:58 -0000
On Jul 15, 5:39 pm, Steve Holden <st...@xxxxxxxxxxxxx> wrote:
xamdam wrote:
Additional info: my file is from a data provider, do not know whatIt could be you are using a Python with an in-built limit of 2GB on file
they used to compress it. Previous files worked ok, this one is the
1st over 2GB. Winzip has no problem with it.
size. What happens if you open the file, seek past the 2GB point and
then try and read data?
Steve,
I used is_zipfile function, which from does exactly that from a quick
read - goes to the end, reads expected string. It worked fine. Tried
regular Windows 2.4.4 and 2.5.1, same result.
Fine, if it isn't file size limitations I suspect you need to post some
code and a traceback so we can get better insight into exactly what the
problem is.
It's failing in the ZipFile constructor, which ends up throwing
zipfile(2.4.3).py:291> raise BadZipfile, "Bad magic number for file
header"
.
- Follow-Ups:
- Re: zipfile 2GB problems?
- From: John Machin
- Re: zipfile 2GB problems?
- From: Steve Holden
- Re: zipfile 2GB problems?
- References:
- zipfile 2GB problems?
- From: xamdam
- Re: zipfile 2GB problems?
- From: xamdam
- Re: zipfile 2GB problems?
- From: Steve Holden
- Re: zipfile 2GB problems?
- From: xamdam
- Re: zipfile 2GB problems?
- From: Steve Holden
- zipfile 2GB problems?
- Prev by Date: Binary blobs to jpeg
- Next by Date: testing with coverage.py problem
- Previous by thread: Re: zipfile 2GB problems?
- Next by thread: Re: zipfile 2GB problems?
- Index(es):
Relevant Pages
|