@@ -93,8 +93,8 @@ This uses setup.py, so it follows the standard Python routine:
93
93
A GNU makefile is also provided so :code: `make install ` (possibly as root or
94
94
sudo) will do the steps above.
95
95
96
- Testing
97
- -------
96
+ Running Tests
97
+ -------------
98
98
99
99
::
100
100
@@ -133,18 +133,8 @@ You can also cross compare the results with pycdc_ . Since they work
133
133
differently, bugs here often aren't in that, and vice versa.
134
134
135
135
136
- Known Bugs/Restrictions
137
- -----------------------
138
-
139
- The biggest known and possibly fixable (but hard) problem has to do
140
- with handling control flow. (Python has probably the most diverse and
141
- screwy set of compound statements I've ever seen; there
142
- are "else" clauses on loops and try blocks that I suspect many
143
- programmers don't know about.)
144
-
145
- All of the Python decompilers that I have looked at have problems
146
- decompiling Python's control flow. In some cases we can detect an
147
- erroneous decompilation and report that.
136
+ Verification
137
+ ------------
148
138
149
139
In older versions of Python it was possible to verify bytecode by
150
140
decompiling bytecode, and then compiling using the Python interpreter
@@ -167,6 +157,19 @@ And already Python has a set of programs like this: the test suite
167
157
for the standard library that comes with Python. We have some
168
158
code in `test/stdlib ` to facilitate this kind of checking.
169
159
160
+ Known Bugs/Restrictions
161
+ -----------------------
162
+
163
+ The biggest known and possibly fixable (but hard) problem has to do
164
+ with handling control flow. (Python has probably the most diverse and
165
+ screwy set of compound statements I've ever seen; there
166
+ are "else" clauses on loops and try blocks that I suspect many
167
+ programmers don't know about.)
168
+
169
+ All of the Python decompilers that I have looked at have problems
170
+ decompiling Python's control flow. In some cases we can detect an
171
+ erroneous decompilation and report that.
172
+
170
173
Python support is strongest in Python 2 for 2.7 and drops off as you
171
174
get further away from that. Support is also probably pretty good for
172
175
python 2.3-2.4 since a lot of the goodness of early the version of the
@@ -194,7 +197,7 @@ Between Python 3.5, 3.6 and 3.7 there have been major changes to the
194
197
195
198
Currently not all Python magic numbers are supported. Specifically in
196
199
some versions of Python, notably Python 3.6, the magic number has
197
- changes several times within a version.
200
+ changes several times within a version.
198
201
199
202
**We support only released versions, not candidate versions. ** Note however
200
203
that the magic of a released version is usually the same as the *last * candidate version prior to release.
0 commit comments