12 Commits

Author	SHA1	Message	Date
rocky	a32c0e68ef	Bang on 3.6 MAKE_FUNCTION a bit more ... parse3.py, parse36.py: adding return_closure rule tags what's going on with this rule pysource.py: start changing semantic rules to support code changed by new make_function semantics README.rst: typo	2017-05-13 10:06:43 -04:00
Daniel Bradburn	ca1679e636	Added support for support for Python 3.6 CALL_FUNCTION_KW	2017-05-10 21:49:42 +02:00
rocky	84fd71b73b	Python 3.6 CALL_FUNCTION_EX first attempt	2017-04-25 07:31:01 -04:00
rocky	8a33a583cd	3.6 generates Wonky EXTENDED_ARG in expression ... Fixes Issue #102	2017-04-15 18:31:39 -04:00
rocky	4827b1e994	Towards better 3.6 support	2017-01-03 00:44:07 -05:00
rocky	e3f4beeb74	Lint	2016-12-24 07:45:02 -05:00
rocky	08dcc7d820	Start to handle 3.5 build_map_unpack_with_call ... 3.6 also started but needs even more work	2016-12-16 20:39:24 -05:00
rocky	9cc2700160	Shorten Python3 grammars with + and *	2016-11-28 23:49:43 -05:00
rocky	0480455ae1	DRY Python 3.6 grammar rules	2016-10-22 12:29:36 -04:00
moagstar	cec80e696c	further work on supporting single and multiple fstring decompilation	2016-10-20 20:44:27 +02:00
moagstar	7beaa9f36c	urther work on fstrings for python 3.6 - there is a new opcode build_string which is used to improve fstring performance, but broke the fstring support in uncompyle	2016-10-19 23:32:15 +02:00
rocky	65a16327ce	Moagstar's 3.6 wordcode + formattedValue rules	2016-08-01 03:16:26 -04:00