From bf195a234f01b34d51dccb8f8c70d8565d534294 Mon Sep 17 00:00:00 2001 From: rocky Date: Sat, 22 Apr 2017 10:57:54 -0400 Subject: [PATCH] Document Python 3.x status --- README.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.rst b/README.rst index 44b93730..1cfcce86 100644 --- a/README.rst +++ b/README.rst @@ -21,7 +21,8 @@ There were a number of decompyle, uncompile, uncompyle2, uncompyle3 forks around. All of them came basically from the same code base, and almost all of them no were no longer actively maintained. Only one handled Python 3, and even there, only 3.2 or 3.3 depending on which -code is used. This code pulls these together and moves forward. It +code is used. This code pulls these together and moves forward. This +project has the most complete support for Python 3.3 and above. It also addresses a number of open issues in the previous forks. What makes this different from other CPython bytecode decompilers?: its @@ -166,7 +167,7 @@ There is lots to do, so please dig in and help. See Also -------- -* https://github.com/zrax/pycdc : supports all versions of Python and is written in C++ +* https://github.com/zrax/pycdc : supports all versions of Python and is written in C++. Support for later Python 3 versions is a bit lacking though. * https://code.google.com/archive/p/unpyc3/ : supports Python 3.2 only. The above projects use a different decompiling technique what is used here. * https://github.com/figment/unpyc3/ : fork of above, but supports Python 3.3 only. Include some fixes like supporting function annotations * The HISTORY_ file.