> [Re forcing all extensions to use PythonExtensionInit_XXX] [GvR] > > I sort-of like this idea -- at least at the +0 level. [MH] > Since this email there have been some strong objections to this. I too > would weigh in at -1 for this, simply for the amount of work it would cost > me personally! OK. Dead it is. -1. > Shall this be checked in to the 1.6 and 2.0 trees? Yes, I'll do so. > "Fatal Python error: Interpreter not initialized" might not be too helpful, > but it's surely better than "PyThreadState_Get: no current thread"... Yes. --Guido van Rossum (home page: http://www.pythonlabs.com/~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