Get ready for release 2.6.1

This commit is contained in:
rocky 2016-07-08 12:13:41 -04:00
parent e020f8f9a9
commit 7fdb4d3e68
4 changed files with 47 additions and 7 deletions

View File

@ -1,3 +1,37 @@
2016-07-08 rocky <rocky@gnu.org>
* README.rst, uncompyle6/version.py: Get ready for release 2.6.1
2016-07-08 rocky <rocky@gnu.org>
* test/simple_source/stmts/11_return_val.py,
uncompyle6/scanners/scanner2.py, uncompyle6/scanners/scanner26.py:
2.5/2.6 RETURN_VALUE bug
2016-07-08 rocky <rocky@gnu.org>
* uncompyle6/parsers/parse25.py, uncompyle6/parsers/parse26.py:
2.5/2.6 fn name clash fixes list conprehension problem
2016-07-08 rocky <rocky@gnu.org>
* uncompyle6/parsers/parse25.py: Python 2.5 with statement
2016-07-08 rocky <rocky@gnu.org>
* README.rst: Revise decompilation quality estimate
2016-07-08 rocky <rocky@gnu.org>
* test/add-test.py, test/simple_source/stmts/05_with.py,
uncompyle6/parser.py, uncompyle6/parsers/parse25.py,
uncompyle6/parsers/parse26.py: Start going over Python 2.5 bytecode Fix 2.6 with bug
2016-07-07 rocky <rocky@gnu.org>
* ChangeLog, NEWS, __pkginfo__.py, uncompyle6/version.py: Get ready
for release 2.6.0
2016-07-07 rocky <rocky@gnu.org>
* uncompyle6/parsers/parse26.py: <2.7 add a rare kind of list_for

6
NEWS
View File

@ -1,3 +1,9 @@
uncompyle6 2.6.1 2016-07-08
- Go over Python 2.5 bytecode deparsing
all library programs now deparse
- Fix a couple bugs in 2.6 deparsing
uncompyle6 2.6.0 2016-07-07
- Improve Python 2.6 bytecode deparsing:

View File

@ -90,12 +90,6 @@ ok. Some of these failures may be bugs in the verification process.
At this point, 2.7 decompilation is better than uncompyle2. A number
of bugs have been fixed over what was in uncompyle2.
Python 2.6 installed library routines decompile; it is probably the
same as uncompyle2, although some 2.6 bugs from uncompyle2 have been
fixed. We handle 2.6 bytecode a little bit differently than the way
uncompyle2 does so it is harder to assess quality. Python 2.5
bytecode may not be as good as uncompyle2, but is catching up.
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.
@ -104,6 +98,12 @@ There are a few constructs that still need to be added to Python 3.5
Python 3.6 changes things drastically by using word codes rather than
byte codes. So that will be yet another challenge
Python 2.5 and 2.6 installed library routines also decompile; it is
probably the same as uncompyle2, although some 2.6 bugs from
uncompyle2 have been fixed. We handle 2.5 and 2.6 bytecode a little
bit differently than the way uncompyle2 does so it is harder to assess
quality.
There is lots to do, so please dig in and help.
See Also

View File

@ -1,3 +1,3 @@
# This file is suitable for sourcing inside bash as
# well as importing into Python
VERSION='2.6.0'
VERSION='2.6.1'