> > i had a quick look at Objects/abstract.c in 2.2.2's source. almost > > every function there checks whether the objects it's passed are not > > NULL. if they are, SystemError exception occurs. since i've never come > > across such exception i've commented out those checks. > Unfortunately, this is part of the safety net for poor extension > writers, and I'm not sure we can drop it. Can we get most of the same benefit by using an assert() rather than NULL-->SystemError? Raymond Hettinger
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