[issue3919] PySys_SetObject crashes after Py_NewInterpreter().

2008-09-21 Thread Graham Dumpleton
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()

[issue3919] PySys_SetObject crashes after Py_NewInterpreter().

2008-09-21 Thread Graham Dumpleton
Graham Dumpleton [EMAIL PROTECTED] added the comment: Sorry, should also mention that this was on MacOS X 10.4 (Tiger). ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3919 ___

[issue3919] PySys_SetObject crashes after Py_NewInterpreter().

2008-09-21 Thread Amaury Forgeot d'Arc
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] http://bugs.python.org/issue3919

[issue3919] PySys_SetObject crashes after Py_NewInterpreter().

2008-09-21 Thread Benjamin Peterson
Changes by Benjamin Peterson [EMAIL PROTECTED]: -- resolution: - duplicate status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3919 ___