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

Wordsmithing

Browse Source
This commit is contained in:
rocky
2017-11-29 05:21:16 -05:00
parent ce20060cc8
commit 1fcccb2472
1 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
README.rst
View File

@@ -20,9 +20,9 @@ Why this?
Ok, I'll say it: this software is amazing. It is a little more than Ok, I'll say it: this software is amazing. It is a little more than
just your normal hacky decompiler. Using compiler_ technology, the just your normal hacky decompiler. Using compiler_ technology, the
program creates a parse tree of the program from the instructions; program creates a parse tree of the program from the instructions;
nodes at the upper levels that look like they come from a Python nodes at the upper levels that look a little like what might come from
AST. So we can really classify and understand what's going on in a Python AST. So we can really classify and understand what's going on
sections of Python bytecode. in sections of Python bytecode.
Building on this, another thing that makes this different from other Building on this, another thing that makes this different from other
CPython bytecode decompilers is the ability to deparse just CPython bytecode decompilers is the ability to deparse just
@@ -40,12 +40,14 @@ be used in showing stack traces or any program that wants to show a
location in more detail than just a line number. It can be also used location in more detail than just a line number. It can be also used
when source-code information does not exist and there is just bytecode when source-code information does not exist and there is just bytecode
There were (and still are) a number of decompyle, uncompyle, uncompyle2, There were (and still are) a number of decompyle, uncompyle,
uncompyle3 forks around. Almost all of them come basically from the uncompyle2, uncompyle3 forks around. Almost all of them come basically
same code base, and (almost?) all of them are no longer actively from the same code base, and (almost?) all of them are no longer
maintained. Only one handled Python 3, and even there, only 3.2 or 3.3 actively maintained. One was really good at decompiling Python 1.5-2.3
depending on which code is used. This code pulls these together and or so, another really good at Python 2.7, but that only. Another
moves forward. handles Python 3.2 only; another patched that and handled only 3.3.
You get the idea. This code pulls all of these forks together and
*moves forward*.
This project has the most complete support for Python 3.3 and above This project has the most complete support for Python 3.3 and above
and the best all-around Python support. and the best all-around Python support.