[Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 Python (original) (raw)
Thomas Wouters thomas@xs4all.net
Fri, 4 Aug 2000 10:14:56 +0200
- Previous message: [Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 Python
- Next message: [Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Aug 04, 2000 at 03:58:52PM +1000, Mark Hammond wrote:
It is now Friday afternoon for me. Regardless of the outcome of this, the patch Fredrik posted recently would still seem reasonable, and not have too much impact on performance (ie, after locating and loading a .dll/.so, one function call isnt too bad!):
+ if (!PyIsInitialized()) + PyFatalError("Interpreter not initialized (version
Wasn't there a problem with this, because the 'Py_FatalError()' would be the one in the uninitialized library and thus result in the same tstate error ? Perhaps it needs a separate error message, that avoids the usual Python cleanup and trickery and just prints the error message and exits ?
-- Thomas Wouters <thomas@xs4all.net>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
- Previous message: [Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 Python
- Next message: [Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]