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

More small history tweaks

Browse Source
This commit is contained in:
rocky
2016-05-09 05:34:01 -04:00
parent e37b197db9
commit 73461d323e
1 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
HISTORY.md
View File

@@ -73,19 +73,19 @@ The project exists not only on
the defunct [google the defunct [google
code](https://code.google.com/archive/p/unpyc/). The git/svn history code](https://code.google.com/archive/p/unpyc/). The git/svn history
goes back to 2009. Somewhere in there the name was changed from goes back to 2009. Somewhere in there the name was changed from
"decompyle" "unpyc" by Keknehv and then to "uncompyle" by Guenther Starnberger. "decompyle" to "unpyc" by Keknehv, and then to "uncompyle" by Guenther Starnberger.
The name Thomas Grainger isn't found in (m)any of the commits in the The name Thomas Grainger isn't found in (m)any of the commits in the
several years of active development. First Keknehv worked on this up several years of active development. First Keknehv worked on this up
to Python 2.5 or so while acceping Python bytecode back to 2.0 or to Python 2.5 or so while acceping Python bytecode back to 2.0 or
so. Then hamled made a few commits earler on while Eike Siewertsen so. Then hamled made a few commits earler on, while Eike Siewertsen
made a few commits later on. But mostly wibiti, and Guenther made a few commits later on. But mostly wibiti, and Guenther
Starnberger got the code to where uncompyle2 was around 2012. Starnberger got the code to where uncompyle2 was around 2012.
This project, uncompyle6, however owes its existence to the fork of This project, uncompyle6, however owes its existence to the fork of
uncompyle2 by Myst herie (Mysterie) whose first commit seems to goes uncompyle2 by Myst herie (Mysterie) whose first commit seems to goes
back to 2012. I chose this as it seemed to have been the most actively, back to 2012. I chose this since it seemed to have been at that time
if briefly, worked on. the most actively, if briefly, worked on.
Over the many years, code styles and Python features have Over the many years, code styles and Python features have
changed. However brilliant the code was and still is, it hasn't really changed. However brilliant the code was and still is, it hasn't really
@@ -100,12 +100,15 @@ Hartmut a decade an a half ago:
NB. This is not a masterpiece of software, but became more like a hack. NB. This is not a masterpiece of software, but became more like a hack.
Probably a complete rewrite would be sensefull. hG/2000-12-27 Probably a complete rewrite would be sensefull. hG/2000-12-27
Lastly, I should mention [unpyc3](https://code.google.com/p/unpyc3/) This project deparses using a LR parse. However another approach is to
and most especially [pycdc](https://github.com/zrax/pycdc), largely by do something like simulate execution symbolically and build expression
Michael Hansen and Darryl Pogue. If they supported getting source-code trees off of stack results. The two important projects that work this
fragments and I could call it from Python, I'd probably ditch this and way are [unpyc3](https://code.google.com/p/unpyc3/) and most
use that. From what I've seen, the code runs blindingly fast and spans especially [pycdc](https://github.com/zrax/pycdc) The latter project
all versions of Python. is largely by Michael Hansen and Darryl Pogue. If they supported
getting source-code fragments and I could call it from Python, I'd
probably ditch this and use that. From what I've seen, the code runs
blindingly fast and spans all versions of Python.
Tests for the project have been, or are being, culled from all of the Tests for the project have been, or are being, culled from all of the
projects mentioned. projects mentioned.