From 04698f45cc4246b95b3bb8c22f61e0398614b344 Mon Sep 17 00:00:00 2001 From: rocky Date: Sun, 3 Jul 2016 11:32:20 -0400 Subject: [PATCH] Update history. Note 2.5-2.6 deficiencies Note Eloi Vanderbeken's contribution --- HISTORY.md | 14 ++++++++++++-- README.rst | 9 +++++---- 2 files changed, 17 insertions(+), 6 deletions(-) diff --git a/HISTORY.md b/HISTORY.md index ef68b947..49f168f3 100644 --- a/HISTORY.md +++ b/HISTORY.md @@ -93,8 +93,18 @@ so. Then hamled made a few commits earler on, while Eike Siewertsen made a few commits later on. But mostly wibiti, and Guenther Starnberger got the code to where uncompyle2 was around 2012. -This project, uncompyle6, however owes its existence to the fork of -uncompyle2 by Myst herie (Mysterie) whose first commit picks up at +In uncompyle2 decompilation of python bytecode 2.5 & 2.6 is done by +transforming the byte code into a a pseudo 2.7 python bytecode and is +based on code from Eloi Vanderbeken. + +This project, uncompyle6, abandons that approach for various +reasons. However the main reason is that we need offsets in fragment +deparsing to be exactly the same, and the transformation process can +remove instructions. Adding instructions with psuedo_offsets is +however okay. + +Uncompyle6, however owes its existence to the fork of uncompyle2 by +Myst herie (Mysterie) whose first commit picks up at 2012. I chose this since it seemed to have been at that time the most actively, if briefly, worked on. Also starting around 2012 is Dark Fenx's uncompyle3 which I used for inspiration for Python3 support. diff --git a/README.rst b/README.rst index 3cd3bcd2..9290782d 100644 --- a/README.rst +++ b/README.rst @@ -86,11 +86,12 @@ Known Bugs/Restrictions Python 2 deparsing decompiles each and all the Python 2.7.10 and 2.7.11 installed packages I have on my system, more than 90% verify -ok. Some of these failures may be bugs in the verification process. So -as such, it is probably a little better than uncompyle2. Other Python -2 versions do worse. +ok. Some of these failures may be bugs in the verification process. +So as such, it is probably a little better than uncompyle2. Python 2.6 +is catching up the versions of uncompyle2 that support 2.6 but is +currently worse. Even less good is Python 2.5 bytecodes. -All of the Python 3.2-3.5.4 Python standard lib packages that I have +All of the Python 3.2-3.5 Python standard lib packages that I have installed on my system deparse. Each Python version has about 200 bytecode files. I'm not sure how well these verify though.