jinx/python-uncompyle6
1
Fork 0
mirror of https://github.com/rocky/python-uncompyle6.git synced 2025-08-03 16:59:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

Limitations of decompiling control structures.

Browse Source
This commit is contained in:
rocky
2016-11-27 14:20:35 -05:00
parent 69c93cc665
commit 0d0f836f76
1 changed files with 13 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
README.rst
View File

@@ -97,7 +97,8 @@ Known Bugs/Restrictions
----------------------- -----------------------
The biggest known and possibly fixable (but hard) problem has to do The biggest known and possibly fixable (but hard) problem has to do
with handling control flow. In some cases we can detect an erroneous with handling control flow. All of the Python decomilers I have looked
at have the same problem. In some cases we can detect an erroneous
decompilation and report that. decompilation and report that.
About 90% of the decompilation of Python standard library packages in About 90% of the decompilation of Python standard library packages in
@@ -109,14 +110,17 @@ Other versions drop off in quality too.
a Python for that bytecode version, and then comparing the bytecode a Python for that bytecode version, and then comparing the bytecode
produced by the decompiled/compiled program. Some allowance is made produced by the decompiled/compiled program. Some allowance is made
for inessential differences. But other semantically equivalent for inessential differences. But other semantically equivalent
differences are not caught. For example ``if x: foo()`` is differences are not caught. For example ``1 and 0`` is decompiled to
equivalent to ``x and foo()`` and decompilation may turn one into the the equivalent ``0``; remnants of the first true evaluation (1) is
other. *Weak Verification* on the other hand doesn't check bytecode lost when Python compiles this. When Python next compiles ``0`` the
for equivalence but does check to see if the resulting decompiled resulting code is simpler.
source is a valid Python program by running the Python
interpreter. Because the Python language has changed so much, for best *Weak Verification*
results you should use the same Python Version in checking as used in on the other hand doesn't check bytecode for equivalence but does
the bytecode. check to see if the resulting decompiled source is a valid Python
program by running the Python interpreter. Because the Python language
has changed so much, for best results you should use the same Python
Version in checking as used in the bytecode.
Later distributions average about 200 files. There is some work to do Later distributions average about 200 files. There is some work to do
on the lower end Python versions which is more difficult for us to on the lower end Python versions which is more difficult for us to