Python Zipfile.badzipfile Bad Magic Number For Central Directory

717 views

Skip to first unread message

Nichole Wernett

unread,

May 1, 2024, 7:42:57 PM5/1/24

to cipupectcho

Ok, so basically I'm trying to write simple quick script in python to search xml from *.fla (flash) files. All I'm doing, is opening *.fla files from project via zipfile.ZipFile, go through all files in this zip archive, and search specific term by regex (dirty and simple). This is not the ideal solution for my problem, but this will work for now. I'm using CS6, and I know that *.fla files from CS5 and above are basically zip archives with xml (and other files) inside, and I have successfully extracted those files via 7zip on windows. But somewhy, on half the files from my project, zipfile.ZipFile throws an exception 'Bad magic number for central directory' on creation. The call stack looks like this:

You hex dump shows the start of the file and the first 4 bytes are indeed a valid local header signature. The problem is the python code is complaining about the central directory header - this is near the end of the file.

python zipfile.badzipfile bad magic number for central directory

DOWNLOAD –––––>>> https://t.co/ookpz9ZlIb

Bad magic number, appears whenever the header (magic number in python) of the compiled byte-code is either corrupted or when you try to running a pyc from a different version of python (usually later) than your interpreter. There are two solutions to rectify this runtime error:

The "magic number" comes from UNIX-type systems where the first few bytes of a file held a marker indicating the file type. Python puts a similar marker into its pyc files when it creates them. The Python interpreter ensures that this number is correct when loading the file.

Anything that damages this magic number will cause the error. This includes editing the .pyc file or trying to run a .pyc file from a different version of Python (usually later) than your interpreter.

importerror: bad magic number error occurs mainly in random module python with Ubuntu operating system because of byte prefix in .pyc file. Actually, what happens with unix-oriented operating systems, The operating system assigns the first few BYTES of the file as an identifier or marker with the file. This is nothing but the magic numbers. The same applies to .pyc files of python. Now if someone tries to use a different Python interpreter or make changes in those .pyc files. The python interpreter throws a bad magic number error. This is the root cause of the following error.

As an aside, the first word of all my 2.5.1(r251:54863) pyc files is 62131, 2.6.1(r261:67517) is 62161. The list of all magic numbers can be found in Python/import.c, reproduced here for completeness (current as at the time the answer was posted, it may have changed since then):

>> I need to save a fairly large set of arrays to disk. I have saved it using
>> numpy.savez, and the resulting file is around 11Gb (yes, I did say fairly
>> large ;D). When I try to load it using numpy.load, the zipfile module
>> compains about
>> BadZipfile: Bad magic number for file header
>>
>> I can't open it with the normal zip utility present on the system, but it
>> could be that it's barfing about files being larger than 2Gb.
>> Is there some file limit for npzs?
>
> Yes, the ZIP file format has a 4GB limit. Unfortunately, Python does
> not yet support the ZIP64 format.
>
>> Is there anyway I can recover the data (I
>> guess I could try decompressing the file with 7z and extracting the
>> individual npy files?)
>
> Possibly. However, if the normal zip utility isn't working, 7z
> probably won't, either. Worth a try, though.

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>>> I need to save a fairly large set of arrays to disk. I have saved it using
>>> numpy.savez, and the resulting file is around 11Gb (yes, I did say fairly
>>> large ;D). When I try to load it using numpy.load, the zipfile module
>>> compains about
>>> BadZipfile: Bad magic number for file header
>>>
>>> I can't open it with the normal zip utility present on the system, but it
>>> could be that it's barfing about files being larger than 2Gb.
>>> Is there some file limit for npzs?
>>
>> Yes, the ZIP file format has a 4GB limit. Unfortunately, Python does
>> not yet support the ZIP64 format.
>>
>>> Is there anyway I can recover the data (I
>>> guess I could try decompressing the file with 7z and extracting the
>>> individual npy files?)
>>
>> Possibly. However, if the normal zip utility isn't working, 7z
>> probably won't, either. Worth a try, though.
>
> I've had similar problems, my solution was to move to HDF5. There are
> two options for accessing and working with HDF files from python: h5py
> ( ) and pytables
> ( ). Both packages have built in numpy support.
>
> Regards,
> Lafras

I am trying to upload excel (.xlsx) file to s3 and read and extract data to save in DBIn my local machine code is working fine when I deployed to lambda then this error is raised raise BadZipFile("Bad magic number for central directory")

Cause Anything that damages this magic number will cause the error. This includes editing the .pyc file or trying to run a .pyc file from a different version of Python (usually later) than your interpreter.

gh-89792: test_tools now copies up to 10x less source data to atemporary directory during the freeze test by ignoring git metadataand other artifacts. It also limits its python build parallelism based onos.cpu_count instead of hard coding it as 8 cores.

gh-92345: pymain_run_python() now imports readline andrlcompleter before sys.path is extended to include the current workingdirectory of an interactive interpreter. Non-interactive interpreters arenot affected.

End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of create_tables.sql.gz or create_tables.sql.gz.zip, and cannot find create_tables.sql.gz.ZIP, period."

Once you have the Word document created, merging the values is a simple operation.The code below contains the standard imports and defines the name of theWord file. In most cases, you will need to include the full path to the templatebut for simplicity, I am assuming it is in the same directory as your python scripts:

The central directory is at the end of the zip file.It is a list of central directory headers.Each central directory header contains metadata for a single file,like its filename and CRC-32 checksum,and a backwards pointer to a local file header.A central directory header is 46 bytes long,plus the length of the filename.

By compressing a long string of repeated bytes,we can produce a kernelof highly compressed data.By itself, the kernel's compression ratio cannotexceed the DEFLATE limit of 1032,so we want a way to reuse the kernel in many files,without making a separate copy of it in each file.We can do it by overlapping files:making many central directory headers point toa single file, whose data is the kernel.

We could make every central directory header have the same filenameas the local file header, but that too is unsatisfyingbecause it means that if extracted to disk,all the files will just overwrite each other and not take up more spacethan a single file.

This quoted-overlap construction has better compatibilitythan the full-overlap construction of the previous section,but the compatibility comes at the expense of the compression ratio.There, each added file cost only a central directory header;here, it costs a central directory header,a local file header,and another 5 bytes for the quoting header.