jinx/python-uncompyle6
1
Fork 0
mirror of https://github.com/rocky/python-uncompyle6.git synced 2025-08-03 16:59:52 +08:00
Code Issues Packages Projects Releases Wiki Activity
668 Commits 10 Branches 160 Tags
f1bb40f48592cf1381feae4a7fe6bee60041fe68
Commit Graph

44 Commits

Author SHA1 Message Date
rocky
f1bb40f485 Python 2.6- bug: RETURN_ENDIF, POP_TOP .. 
POP_TOP should be excluded as a potentional statement beginning
 2016-09-02 21:08:44 -04:00
rocky
1d567d5d9a Handle Python 2.6 and below "except <cond>, <var>" 2016-09-01 02:20:07 -04:00
rocky
e8ed17967c Clean and check Python 2.6 grammar 2016-07-27 18:03:07 -04:00
rocky
3f7c4209d9 Start to segregate and clean up grammar 2016-07-27 17:35:21 -04:00
rocky
5ffd9b2be7 2.6 and 2.7 while1 grammar rule 
Fixes issue #40
 2016-07-27 13:19:42 -04:00
rocky
9fdf70f68d Python 3.(4?) while1 bug 
Clean up while1 grammar a tad
 2016-07-11 10:18:18 -04:00
rocky
b640d42113 2.5/2.6 fn name clash 
fixes list conprehension problem
 2016-07-08 10:38:56 -04:00
rocky
6f5dce342f Start going over Python 2.5 bytecode 
Fix 2.6 with bug
 2016-07-08 07:01:48 -04:00
rocky
13ae869267 <2.7 add a rare kind of list_for 2016-07-07 18:03:44 -04:00
rocky
06023c247d while1 bug in 2.6 and 2.7 2016-07-07 13:08:00 -04:00
rocky
21314c1dad <2.7 whileelse rule 2016-07-07 12:11:45 -04:00
rocky
8b305f78f4 2.6 POP_TOP and POP_JUMP_IF bugs 2016-07-07 07:03:20 -04:00
rocky
f865ecaa58 2.6.9 bug: multiple COME_FROMs via "or"/"assert" 2016-07-06 21:07:40 -04:00
rocky
14b4f8e2da 2.6.9 elif with multiple COME_FROMs 2016-07-06 20:56:29 -04:00
rocky
a34f1fcd7a Merge branch 'master' of github.com:rocky/python-uncompyle6 
Conflicts:
	uncompyle6/parsers/parse26.py
 2016-07-03 12:08:37 -04:00
rocky
974b11ff55 Another 2.6 while stmt. Clean up grammar a little 2016-07-03 10:50:19 -04:00
rocky
4d9d659cfa 2.6 improper tagging of RETURN_END_IF 2016-07-03 04:33:43 -04:00
rocky
bec1524c5a 2.6.9 tryelsestmt 2016-07-02 22:53:58 -04:00
rocky
12d22c055f Python 2.6 with as stmt 2016-07-02 22:24:28 -04:00
rocky
4dff02b19c 2.6 ifelsestmt 2016-07-01 17:15:00 -04:00
rocky
71822bf9b3 Another 2.6 return_stmt bug 2016-07-01 07:51:15 -04:00
rocky
fa6ae76a64 2.6 return_stmt bug 2016-07-01 06:50:06 -04:00
rocky
261c60efd9 More 2.6.9 bugs fixed 
* break loop parsing bug
* ifelsestmt semantic-action bug in handling else
 2016-06-30 21:42:49 -04:00
rocky
d87b5fe34c 2.6 conditional in list comprehension bug 2016-06-30 19:51:13 -04:00
rocky
73a043830c 2.6.9 list comprehension 2016-06-30 06:51:20 -04:00
rocky
7772243ac7 CONTINUE handling in 2.6.9 2016-06-30 05:32:57 -04:00
rocky
f573013501 2.6 except_suite bug 2016-06-30 05:09:14 -04:00
rocky
4b0b7f76dc 2.6 genexpr. Some not quite right. 2016-06-29 23:32:29 -04:00
rocky
d7f7748000 2.6.9 assert 2-arg bug 2016-06-29 22:28:52 -04:00
rocky
5b2198a4a6 A 2.6 comprehension bug 2016-06-29 21:24:19 -04:00
rocky
32ca0c4482 2.6 ifelse/while modifications 2016-06-29 12:46:02 -04:00
rocky
0af3dd28bc Weird 2.6.9 list comprehension 2016-06-28 17:37:13 -04:00
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
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
rocky
724faf9a3a Go over grammars.. 
* Reduce duplication
* Remove unused grammar rules
* Add grammar checking when parsers run as standalone
 2016-06-17 22:59:17 -04:00
rocky
3da4c9ce77 Start custom grammar for 2.6 and ... 
fix a python 2.6.9 deparse with lc if+and+not
 2016-06-02 19:16:27 -04:00