> If the initialization of type objects is all that needs fixing to > get Python compile to on MinGW32, why not simply fix it ? Gerhard indicated all is working now. > MSVC has had > the same problem for years. What's strange is that in some cases, > MSVC does seem to get it right where in others it fails with an > error -- probably a DLL vs. EXE thing. It is a problem for extension modules. Object files in the core DLL have no problem, but object modules in seperate extension DLLs that reference the global in pythonxx.dll generate the error. Thus, we see the error as modules are split out of the core - eg, _socket, _winreg, etc. Mark.
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