> Suggest replacing it with:
>
> assert(!"Invalid argument to DUP_TOPX");
Actually, I would recommend
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.
--Guido van Rossum (home page: http://www.python.org/~guido/)
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