Oct. 11, 2000
3:03 p.m.
Can't user Python code, fiddling around with bytecode, produce garbled bytecode? In that case, it seems even better to raise an exception.
Yes, they can produce garbled bytecode, and if that is detected, it's not safe to proceed. So a fatal error is the right thing.
The problem with letting Python code cause fatal errors is that it makes restricted execution much more difficult. Well, something to think about for 2.1...
Huh? In restricted execution you shouldn't be allowed to mess with bytecode! --Guido van Rossum (home page: http://www.python.org/~guido/)