rocky
36432c7488
Add more come_from_pops
2016-06-28 14:43:58 -04:00
rocky
74c6b38fd8
2.6. with fn()
2016-06-28 10:54:01 -04:00
rocky
ae980e4f64
Base 2.5 off of 2.6. Some other small bugs.
2016-06-28 03:31:32 -04:00
rocky
21216b4eb1
2.6 try except hadnling works now
2016-06-27 21:54:29 -04:00
rocky
40d4348757
2.6 list comprehensions
2016-06-27 17:53:06 -04:00
rocky
622f83970b
JUMP_IF_{TRUE,FALSE}_OR_OP fixes
2016-06-27 17:15:21 -04:00
rocky
460ad129cc
WIP 2.6 j{f,b}_pop fix
2016-06-27 16:16:35 -04:00
rocky
fa84f4277a
WIP deal with JUMP_IF_{TRUE,FALSE} vs with POP version
2016-06-24 20:06:10 -04:00
rocky
fa7d8f955a
WIP Python-2.6 but don't remove opcodes
...
The scheme for turning 2.6 bytecode into 2.7 psuedo bytecode
I think is a lose.
I won't work for fragment handling.
Instead, change the grammar and syntax rules
This also has the benefits:
* We see how code generation changed over releases
by looking at grammar and semantic rules rather
than arbitrary code
* We can better assocate with what's running
(in a sense this is a restatement of broken fragment
handling)
* With the right structure in place we are in a better position to
handle 2.5, 2.4, etc. That is, after a while, the incremental changes
to get say from python 2.3 bytecode to python 2.7 are great.
Conflicts:
uncompyle6/parsers/astnode.py
2016-06-24 18:15:59 -04:00
rocky
fe8000e02a
Small misfeature disassemble showasm parameter use
2016-06-24 15:05:14 -04:00
rocky
4fa68b8894
2.6 compatibility
2016-06-24 10:36:36 -04:00
rocky
36b7521597
Small formating changes ...
...
and premonition of 2.6 byteocde work
2016-06-24 09:47:45 -04:00
rocky
f474ea648b
Merge branch 'master' of github.com:rocky/python-uncompyle6
2016-06-24 09:29:20 -04:00
rocky
7a4e3a05ff
Should use xdis 1.1.2 + small lint change
2016-06-24 09:28:50 -04:00
rocky
982a6010a1
WIP 2.6 redo bytecode handling
...
Don't try to convert 2.6 bytecode to 2.7 psuedo bytecode.
Instead adjust grammar and semantic actions.
Down the line we should to segregate version changes in
semantic code better.
2016-06-24 09:23:30 -04:00
Daniel Bradburn
c9fd86e38e
fixed bug in maybe_show_ast_param_default, if default was not a str a TypeError would occur
2016-06-24 08:49:37 +02:00
rocky
9a251b239e
Doc fixes
2016-06-22 23:42:33 -04:00
rocky
1563e16f9f
Get ready for release 2.5.0
2016-06-22 22:52:32 -04:00
rocky
e2917590fc
Update README
2016-06-22 22:31:19 -04:00
rocky
493ffa62fe
Python 3.5 and setcomp_func's
...
A comprehension walk in Python 3.5 needs to include
setcomp_func's.
2016-06-22 22:21:54 -04:00
rocky
9a2369830d
Python 3.5 if handling...
...
Allow RETURN_END_IF in a return statement
May want to do this in other versions as well, but right now
we only need it here.
2016-06-22 22:09:06 -04:00
rocky
f999e6a33a
Another kind of yield_from on 3.5
2016-06-22 16:48:03 -04:00
rocky
126af429fb
differing ways to do "yield from" in 3.3-3.5
2016-06-22 16:29:58 -04:00
rocky
480e6a125f
Add Python 3.5 yield from and ...
...
* fragments.py: Handle pass stmt sometimes
* scanners: regularize Python 2 scanners some
* test/test_pyenvlib.py: add python 3.5.1 option
2016-06-22 13:08:11 -04:00
rocky
faa630902d
Python 3 comprehension fixes
...
Sync up fragments.py
2016-06-22 10:50:11 -04:00
rocky
f576853f19
More 3.2 LOAD_CONST removal
...
More python3 custom grammar DRYing
2016-06-22 09:52:20 -04:00
rocky
dc88bcf69f
DRY parse grammar a little
...
More LOAD_CONST grammar removal in 3.2
2016-06-22 08:36:01 -04:00
rocky
c77e4a9dc9
Python 3.2 MAKE_FUNCTION adjustment
2016-06-22 02:11:59 -04:00
rocky
75592795b3
Python 2.6 tolerance
2016-06-22 00:05:19 -04:00
rocky
649da8fbc0
Btter Python 3 fragment set comprehensions ...
...
fragment handling for "break" and "continue"
2016-06-21 23:40:26 -04:00
rocky
cdb02fa591
Handle fragment key/value offsets better
2016-06-21 04:08:36 -04:00
rocky
051ed90185
Bang on Python 3.2 decompiling.
2016-06-20 23:05:12 -04:00
rocky
1a83c849dc
Python 3 needs Python2's RETURN_END_IF
...
Make python2 and python3 scanner look more the same
2016-06-20 22:12:29 -04:00
rocky
a6fbe4c636
previous 2.7 class decorator bug fixed in 3.x
2016-06-20 20:19:17 -04:00
rocky
f215888374
DRY redundant custom rule checking code
2016-06-20 19:06:45 -04:00
rocky
24d4cfb150
Python 3 set comprehension bug
2016-06-20 18:47:03 -04:00
rocky
59780483a8
Python 3.x class bug using subclass fns
2016-06-20 17:20:47 -04:00
rocky
80cfe62f36
For Python 3: add LOAD_CLASSDEREF op
2016-06-20 13:04:21 -04:00
rocky
8c374904f5
3.x make closure kw args handling bug
2016-06-20 10:01:18 -04:00
rocky
078f15013e
Python 3.x class decorator bug
2016-06-20 00:32:00 -04:00
rocky
efb4012087
Correct kw+pos args semantics on 3.3
...
Sync fragment make_function code
2016-06-19 21:41:40 -04:00
rocky
8b50dda9ef
Start 3.3 positional and kw parameters
...
Semantic routines need more work.
2016-06-19 19:18:45 -04:00
rocky
bd809dc08b
Another 3.x bug involving jumps
2016-06-19 17:47:43 -04:00
rocky
109d99bc62
Revert assert test on 3.4 until we figure out how to address
2016-06-19 13:59:24 -04:00
rocky
5c268ee2a6
2.7 and 3.x bug in dict comprehensions
2016-06-19 13:45:07 -04:00
rocky
520290898b
3.4 Load assert bug
2016-06-19 11:52:38 -04:00
rocky
f8ccb8065e
3.4 tryifelse bug
2016-06-19 11:15:36 -04:00
rocky
5d86a4e536
Python 3 except clause parsing bug
2016-06-19 10:30:39 -04:00
rocky
ff014a8393
Cover more offsets
2016-06-19 04:22:55 -04:00
rocky
2c22e86562
Python 3.3 is more like 3.4 than we had thought?
2016-06-19 03:23:25 -04:00
