Unable to decompile any .pyc file about uncompyle2 HOT 9 CLOSED

Hi,
That magic number is "newer" than the the most recent python 2.7.3 release.
Maybe it's from a pre-release version of 2.7.4. Or it could be from a custom python version.
You could try adding 62215 to the magic numbers in magics.py.

from uncompyle2.

Hi,

After adding the magic number in magics.py file, now its giving me "ValueError: bad marshal data (unknown type code)"

Is this error specific to uncompyle2 or python?

For different files there are different errors, can you please give me any specific file that can be compiled back to .py

Thanks,
Vimarsh

from uncompyle2.

That error comes from the marshal module which is a standard python module. The marshal module is used by python to serialize python objects, particularly code objects. Uncompyle2 uses the marshal module to unserialize the code in a pyc file into a live python code object. Usually the marshal format doesn't change much between versions of python, but that error indicates that the version of python which generated your .pyc files has changed the marshal format enough to no longer be compatible with the version of python which is executing uncompyle2.

You can see the marshal type codes of the latest python 2.7 release here: http://svn.python.org/projects/python/branches/release27-maint/Python/marshal.c

from uncompyle2.

Hi wibiti,

Thanks for the information you are providing, according to your last reply does it mean files I am trying are not compatible with uncompyle2.

And does 2.7 means 2.7.x (x = 3 or any version number) compiled file will not work with 2.7 uncompyle2?

Thanks,
Vimarsh

from uncompyle2.

uncompyle2 should work with 2.7.1 through 2.7.3. I'm not sure about 2.7.0
or prerelease versions of 2.7. There are still bugs, but it will decompile
the majority of such files, and I try to fix bugs that are reported.

I'm not sure what version of python generated your .pyc files, but from the
magic number error we know it's not from any released version of python 2.7

There is a chance that if you have the version of python that compiled
those files and used that version of python to run uncompyle2 then it might
work. At least you wouldn't get the marshal error, but most likely you'd
get some other error. You could implement your own marshal. Uncompyle2
used to use it's own marshal implementation before switching to using the
standard python marshal.
https://github.com/wibiti/uncompyle2/blob/428ab87733fe00789ac9a861c1ae686d5bf3e731/uncompyle2/marshal.py

On Thu, Feb 21, 2013 at 7:10 AM, Vimarsh N Sharma
[email protected]:

Hi wibiti,

Thanks for the information you are providing, according to your last reply
does it mean files I am trying are not compatible with uncompyle2.

And does 2.7 means 2.7.x (x = 3 or any version number) compiled file will
not work with 2.7 uncompyle2?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23#issuecomment-13887814.

from uncompyle2.

Hi wibiti,

I want to get some files decompiled, if you feel fine can you please send me your details to my email address [email protected] so I can send you files as files are important for me.

Thanks,
Vimarsh

from uncompyle2.

Hi Vimarsh,

I don't have a lot of time available for this kind of work. I'm sorry uncompyle2 isn't able to decompile your files.
There is another branch of uncompyle2 here: https://github.com/Mysterie/uncompyle2. You could try asking for help there. Sorry.

from uncompyle2.

Hi wibiti,

Thanks for co-operation, I will go through the link you have suggested and meanwhile I will ask if I came through any error or help.

Thanks,
Vimarsh

from uncompyle2.

I am also facing the same issue. After adding the magic number (62215) I am getting this error, ValueError: bad marshal data (unknown type code). I also tried this one https://github.com/Mysterie/uncompyle2 but still same issues.

Vimarsh,

Can you able to decompile after that ?

I would appreciate if someone can guide me to retrieve files from that. Please let me know if you need any sample file having the problem.

Thanks,
Venkatesh

from uncompyle2.