> It's not a particularly sane piece of code, and I'm not saying the > code should _work_, but I'm not so sure a SystemError is appropriate > here. Indeed. PyErr_BadInternalCall() should only be used for cases where it's certain that the bad argment must have been created by a broken piece of C code. Poor Python code should never be allowed to get this invoked. (There are more violations of this principle, but that's the principle nevertheless, and those violations are just that.) --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