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

Note what's up with Python 3 decompile quality

Browse Source
This commit is contained in:
rocky
2017-01-03 07:38:01 -05:00
parent e4c0d56947
commit 77caf515ea
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.rst
View File

@@ -138,10 +138,13 @@ on the lower end Python versions which is more difficult for us to
handle since we don't have a Python interpreter for versions 1.5, 1.6, handle since we don't have a Python interpreter for versions 1.5, 1.6,
and 2.0. and 2.0.
Python 3.0 support is weak; Python 3.5 largely works, but still has In the Python 3 series, Python support is is strongest around 3.4 or
some bugs in it. Python 3.6 changes things drastically by using word 3.3 and drops off as you move further away from those versions. Python
codes rather than byte codes. That has been addressed, but then it also 3.5 largely works, but still has some bugs in it and is missing some
changes function call opcodes and its semantics. opcodes. Python 3.6 changes things drastically by using word codes
rather than byte codes. That has been addressed, but then it also
changes function call opcodes and its semantics and has more problems
with control flow than 3.5 has.
Currently not all Python magic numbers are supported. Specifically in Currently not all Python magic numbers are supported. Specifically in
some versions of Python, notably Python 3.6, the magic number has some versions of Python, notably Python 3.6, the magic number has