[issue3919] PySys_SetObject crashes after Py_NewInterpreter().

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- resolution: -> duplicate status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3919] PySys_SetObject crashes after Py_NewInterpreter().

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: This seems a duplicate of issue3723. -- nosy: +amaury.forgeotdarc superseder: -> Py_NewInterpreter does not work ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3919] PySys_SetObject crashes after Py_NewInterpreter().

Graham Dumpleton <[EMAIL PROTECTED]> added the comment: Sorry, should also mention that this was on MacOS X 10.4 (Tiger). ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3919] PySys_SetObject crashes after Py_NewInterpreter().

New submission from Graham Dumpleton <[EMAIL PROTECTED]>: Somewhere between Python 3.0a3 and Python 3.0b3, a call to PySys_SetObject() after having used Py_NewInterpreter() to create a sub interpreter causes a crash. This appears to be due to interp->sysdict being NULL after Py_NewInterpreter(