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

Update README.rst status on early Pythons

Browse Source
This commit is contained in:
rocky
2020-07-06 12:02:59 -04:00
parent ef59b9c304
commit 430fd2fa85
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.rst
View File

@@ -173,9 +173,9 @@ erroneous decompilation and report that.
Python support is pretty good for Python 2 Python support is pretty good for Python 2
There is some work to do on the lower end Python versions which is On the lower end of Python versions, decompilation seems pretty good although
more difficult for us to handle since we don't have a Python we don't have any automated testing in place for Python's distributed tests.
interpreter for versions 1.6, and 2.0. Also, we don't have a Python interpreter for versions 1.6, and 2.0.
In the Python 3 series, Python support is is strongest around 3.4 or In the Python 3 series, Python support is is strongest around 3.4 or
3.3 and drops off as you move further away from those versions. Python 3.3 and drops off as you move further away from those versions. Python
@@ -190,7 +190,7 @@ added. So in sum handling control flow by ad hoc means as is currently
done is worse. done is worse.
Between Python 3.5, 3.6, 3.7 there have been major changes to the Between Python 3.5, 3.6, 3.7 there have been major changes to the
:code:`MAKE_FUNCTION` and :code:`CALL_FUNCTION` instructions. Python :code:`MAKE_FUNCTION` and :code:`CALL_FUNCTION` instructions.
Python 3.8 removes :code:`SETUP_LOOP`, :code:`SETUP_EXCEPT`, Python 3.8 removes :code:`SETUP_LOOP`, :code:`SETUP_EXCEPT`,
:code:`BREAK_LOOP`, and :code:`CONTINUE_LOOP`, instructions which may :code:`BREAK_LOOP`, and :code:`CONTINUE_LOOP`, instructions which may