diff options
| author | Simon Robertshaw <simon@hardwired.org.uk> | 2011-10-26 13:50:50 (GMT) |
|---|---|---|
| committer | Simon Robertshaw <simon@hardwired.org.uk> | 2011-10-26 13:50:50 (GMT) |
| commit | e46ef289e142982d7bd592faa7b0f85470364c01 (patch) | |
| tree | cda253e03788f7db0a7cdcd05662f66b4455e298 /src/python/stdlib/test/crashers/bogus_code_obj.py | |
| parent | d0d0d62bbcbb5c3417f8cba419c83bac192ea985 (diff) | |
| download | powder-e46ef289e142982d7bd592faa7b0f85470364c01.zip powder-e46ef289e142982d7bd592faa7b0f85470364c01.tar.gz | |
Remove Python console stuff
Diffstat (limited to 'src/python/stdlib/test/crashers/bogus_code_obj.py')
| -rw-r--r-- | src/python/stdlib/test/crashers/bogus_code_obj.py | 19 |
1 files changed, 0 insertions, 19 deletions
diff --git a/src/python/stdlib/test/crashers/bogus_code_obj.py b/src/python/stdlib/test/crashers/bogus_code_obj.py deleted file mode 100644 index 613ae51..0000000 --- a/src/python/stdlib/test/crashers/bogus_code_obj.py +++ /dev/null @@ -1,19 +0,0 @@ -""" -Broken bytecode objects can easily crash the interpreter. - -This is not going to be fixed. It is generally agreed that there is no -point in writing a bytecode verifier and putting it in CPython just for -this. Moreover, a verifier is bound to accept only a subset of all safe -bytecodes, so it could lead to unnecessary breakage. - -For security purposes, "restricted" interpreters are not going to let -the user build or load random bytecodes anyway. Otherwise, this is a -"won't fix" case. - -""" - -import types - -co = types.CodeType(0, 0, 0, 0, '\x04\x71\x00\x00', (), - (), (), '', '', 1, '') -exec co |