> Why should we insert the Py_ prefix? We can just use autoconf to test for > the types. If present, then we use them. If not, then we define our own > replacements. > > I see no particular reason to complicate it with Py_. Defensive coding. If the names are somehow present on the system but somehow not detected by configure, Python.h would run into trouble when it tries to define them when they are in fact already defined by some 3rd party extensiom module that includes the necessary magic to reveal the system definitinons for these names... --Guido van Rossum (home page: http://dinsdale.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