On Wed, 11 Oct 2000, Guido van Rossum wrote:
> Py_FatalError("Invalid argument to DUP_TOPX")
>
> It's not quite the same since it also triggers in release mode. If,
> as Thomas says, this should never happen and can only be caused by
> garbled bytecode, a fatal error is proper rather than a SystemError.
Can't user Python code, fiddling around with bytecode, produce garbled
bytecode? In that case, it seems even better to raise an exception.
Unless I misunderstand the discussion completely.
jumping-to-discussions-in-the-middle-ly y'rs, Z.
--
Moshe Zadka <moshez@math.huji.ac.il>
There is no IGLU cabal.
http://advogato.org/person/moshez
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4