rocky
d7f898b4fb
New feature: show line number correspondences
...
Option --linemap on uncompile show how original source-code line numbers
map to uncompiled source lines
2016-11-18 09:02:00 -05:00
rocky
0f719d41fd
Revise MANIFEST.in with what we have
2016-11-14 20:20:07 -05:00
rocky
6073c77921
Show line numbers in 2.6 "after" asm ..
...
start to understand some of the Python 2.6 bytecode parse failures.
2016-11-14 00:30:23 -05:00
rocky
b6e53205dd
Handle verify syntax errors...
...
Update README.rst stats
2016-11-13 18:55:23 -05:00
rocky
ee6dddd25a
Administrivia: Fixes #66
2016-11-13 14:20:36 -05:00
rocky
968a54512b
Get ready for release 2.9.5
release-2.9.5
2016-11-13 10:37:51 -05:00
rocky
a81ffe8963
Python 3 bugs ...
...
- Was using "while 1 .. else" improperly
- docstring indent bug: was indenting docstring improperly
2016-11-13 10:08:41 -05:00
rocky
3b9e48a3b6
Revise what works and what doesn't
2016-11-13 09:07:53 -05:00
rocky
80a4ad4f1b
Python 3.0 while1 if bug...
...
Is a workaround. We really need more tagging in of SETUP_LOOP and COME_FROM.
2016-11-13 01:28:36 -05:00
rocky
50c2e1bda9
Revert augassign change but..
...
Make note of what's going on and add grammar test for bad
situations we have in Python 2.6 (and perhaps others)
2016-11-11 09:08:02 -05:00
rocky
f4999f6300
augassign semantic action bug
2016-11-11 08:41:55 -05:00
rocky
0f536b18fa
Bug in detecting 3.3 default value in lambda
2016-11-10 23:59:51 -05:00
rocky
6fb879d0d8
Detect some erroneous decompilations
...
Until we can actually prevent these in grammar rules, we will warn of
improper decompilations.
Also, we now stop when we hit a decompile error. Previously we were not.
2016-11-10 22:29:39 -05:00
rocky
411eaaeafb
Remove unused imports
2016-11-10 20:10:56 -05:00
rocky
36874c72e2
Possiby tidy grammar
2016-11-07 22:06:37 -05:00
rocky
7343575e55
Bump xdis to get correct 3.0 bytecodes
2016-11-06 18:01:03 -05:00
rocky
fef0567746
Some Python 3.4 grammar rules apply to Python 3.3
2016-11-06 10:00:10 -05:00
rocky
41f360e3dc
Start bytecode 3.0 decompiling
2016-11-06 09:20:46 -05:00
rocky
5d10f7a0b0
Python 3.0 doesn't have POP_JUMP ops...
...
In some ways Python 3.0 code generation is more like Python 2.6 (and
before) than it is Python 2.7 or 3.0.
2016-11-06 08:55:03 -05:00
R. Bernstein
2a5eda631a
Merge pull request #63 from rocky/python-3.0
...
Python 3.0
2016-11-05 21:17:12 -04:00
rocky
a685c60606
Make parse 3.0 be its own thing
2016-11-05 21:02:49 -04:00
rocky
d2ac293cf6
Merge branch 'master' into python-3.0
2016-11-05 21:01:50 -04:00
rocky
cd3cf5ec29
Use L. for line number prefix in asm and AST
2016-11-03 21:26:12 -04:00
rocky
2eaea447eb
Get ready for release 2.9.4
release-2.9.4
2016-11-02 22:44:23 -04:00
rocky
287e98b4b1
Update unpyc3 info.
2016-11-02 20:42:31 -04:00
rocky
63e4c9343f
Clean up annotation grammar a little
2016-11-01 15:50:19 -04:00
rocky
eab653afdd
Full Python 3 annotations
2016-11-01 12:21:27 -04:00
rocky
7700446bb1
Note github unpyc3 and..
...
- Add source to bytecode_2.2/03_class_method.pyc
- more ignore
2016-10-30 21:16:33 -04:00
rocky
bfd2f77fbc
More source-code line indention in make_function..
...
and remove Python 3 situations from make_function2()
2016-10-30 10:39:11 -04:00
rocky
1574bf4e1e
More annotation processing in to make_function
...
Move return-value annotation determination from n_mkfunc_annotate to
make_function_annotate which is where other kinds of annotation handling
will also need to be done.
2016-10-29 16:03:02 -04:00
rocky
2328ca7a55
Break out make_function() into its own file.
...
It is already too complex and will get worse in Python 3.6.
Note: make_function in fragments.py is still inside and
probably needs fixup.
2016-10-29 07:22:58 -04:00
rocky
ccdd37611c
More complete annotate handling
...
Still have a bit of work to do though.
2016-10-28 19:55:17 -04:00
rocky
2e355b6245
Expand annotate return to Python 3.4
2016-10-28 11:33:54 -04:00
rocky
9849f06ff6
Expand annotate handling to 3.3
...
(and possibly 3.2)
- DRY Python 3.1-3.3 grammar a little
2016-10-28 09:01:41 -04:00
rocky
0e7da031b2
Split out 3.1-3.3 parsers from parser3.py
...
This is anticipation of extending annotation to Python 3.2+
2016-10-28 07:07:18 -04:00
rocky
25dd67a135
Clean and fix Python 3 annotate arg return
2016-10-27 13:52:07 -04:00
rocky
1a38d3d9aa
Dependencies stay within 2nd semantic level
release-2.9.3
2016-10-26 18:36:12 -04:00
rocky
de65a2c250
Get ready for release 2.9.3
2016-10-26 08:29:09 -04:00
rocky
7daec3352c
Start to attack Python 3.1 def() -> xx construct
...
Start to localize make_function routines by Python version
2016-10-26 08:20:19 -04:00
rocky
8feb472d51
Split out Python 3.1 parser from rest.
...
__pkginfo__.py: use Python 3.1 bytecode fixes
2016-10-25 21:47:02 -04:00
rocky
7a10917857
Handle Python 3.1 "with ... as" statement
2016-10-25 02:05:10 -04:00
rocky
334f6935b6
Add python 3.1 bytecode testing
2016-10-24 20:49:05 -04:00
rocky
aff920d87b
Python 3.1 "with" statement bug
2016-10-24 20:47:12 -04:00
rocky
6319d33fa0
Python 3.1 compile bug. DRY Python 3.x rules ...
...
via inheritance
2016-10-24 08:50:34 -04:00
rocky
abb61a4d7d
Fix some Python 3.1 bugs
2016-10-24 02:16:23 -04:00
rocky
b54a19c6ff
Start Python 3.0 decoding
...
Fix some Python 3.1 bugs
2016-10-24 02:11:26 -04:00
Daniel Bradburn
a4c943fe0d
Merge pull request #60 from rocky/buildstring
...
Buildstring
2016-10-22 20:08:30 +02:00
rocky
0480455ae1
DRY Python 3.6 grammar rules
2016-10-22 12:29:36 -04:00
rocky
9b7d978944
Move fstring rules inside a 3.6+ check
2016-10-22 11:48:52 -04:00
rocky
a6befdee09
Merge branch 'buildstring' of github.com:moagstar/python-uncompyle6 into buildstring
2016-10-22 07:23:19 -04:00