-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All files decompilation failed #6
Comments
Hi. I'm not sure what the reason is. |
Yes, uncompyle2 is installed. |
I just checked with the latest version of eve, and it's still working on my computer. Does it create any files? If it isn't creating any files at the store_path, then it may not be able to call uncompyle2 successfully or it is unable to create files at the store_path. I probably should add a verbose mode to evedec to help diagnose this type of situation. |
Yeap, it creates a lot of files in my |
Interesting. I made some changes to uncompyle2 recently through github's webui. I may have made a mistake in that process. I'll have to verify that the uncompyle2 files on my machine are the same as what is in the github repository. |
Wait a second. I didn't notice you pointed
Can it be a reason of this issue? |
That might be the problem. I only test evedec with my version of uncompyle2. |
EDIT: installed uncompyle2 from your repository instead of using pip, and reverted back imports from modified uncompyle6 back to uncompyle2, and it worked :) Same here. I had to change uncompyle2 to uncompyle2 in evedec.py because uncompyle2 was throwing an error 'no module found uncompyle2'. Then the same result: some hundreds of decompile failed errors, and a directory full of empy files. |
I comes to this issues for the same problem. after installed your version of uncompyle2, it decompiles successfully just leave a note here for these comes later |
Hi
I have an issue
After script finishes I see a message: "decompiled 5434 files: 0 okay, 5434 failed"
What could be a reason and how to fix?
python 2.7.15,
The text was updated successfully, but these errors were encountered: