| 1 |
""" |
| 2 |
Broken bytecode objects can easily crash the interpreter. |
| 3 |
|
| 4 |
This is not going to be fixed. It is generally agreed that there is no |
| 5 |
point in writing a bytecode verifier and putting it in CPython just for |
| 6 |
this. Moreover, a verifier is bound to accept only a subset of all safe |
| 7 |
bytecodes, so it could lead to unnecessary breakage. |
| 8 |
|
| 9 |
For security purposes, "restricted" interpreters are not going to let |
| 10 |
the user build or load random bytecodes anyway. Otherwise, this is a |
| 11 |
"won't fix" case. |
| 12 |
|
| 13 |
""" |
| 14 |
|
| 15 |
def f(): |
| 16 |
pass |
| 17 |
|
| 18 |
f.__code__ = f.__code__.replace(co_code=b"") |
| 19 |
f() |