> I read in the archives the problem with import of a 1.5 extension > into newer Python release crashing say new Python. > > A solution that works is to use a new naming scheme for the > initialisation entry point. Currently it is "init" + module-name > with "_d" appended if it is debug image. > > Change "init" to "init16", "init20" and you can import the old > 1.5 linked extension without a crash, you get an error reported > instead. Nice idea... Unfortunately it means that every module must be changed. If we want to do this, we'd best introduce a macro! E.g. (untested): #define Py_INIT(modname) DL_EXPORT(void) init20##modname() --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