[issue3723] Py_NewInterpreter does not work

Christian Heimes <[EMAIL PROTECTED]> added the comment: Applied in r67057 -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3723] Py_NewInterpreter does not work

Graham Dumpleton <[EMAIL PROTECTED]> added the comment: In conjunction with #4213, the attached subinterpreter.patch appears to fix issue for mod_wsgi. ___ Python tracker <[EMAIL PROTECTED]> _

[issue3723] Py_NewInterpreter does not work

Christian Heimes <[EMAIL PROTECTED]> added the comment: In combination with the patch in #4213, "subinterpreter.patch" fixes the problem. I'm assigning the bug to Barry for his final decision. -- assignee: -> barry nosy: +barry type: -> behavior __

[issue3723] Py_NewInterpreter does not work

Changes by Christian Heimes <[EMAIL PROTECTED]>: -- dependencies: +Lower case file system encoding ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3723] Py_NewInterpreter does not work

Christian Heimes <[EMAIL PROTECTED]> added the comment: The patch "subinterpreter.patch" is based on Martin's patch "importexc.diff". The patch contains additional code to setup a preliminary stderr object and a call to initstdio(). Amaury is right. I had to add initstdio() to initialize the stan

[issue3723] Py_NewInterpreter does not work

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > Wouldn't it make more sense to move interpreter initialization things to > Py_NewInterpreter and call it from Py_InitializeEx? Can you propose a specific patch? I'm worried that doing so blindly introduces other bugs.

[issue3723] Py_NewInterpreter does not work

Christian Heimes <[EMAIL PROTECTED]> added the comment: Sounds like a good plan, Benjamin -- nosy: +christian.heimes ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3723] Py_NewInterpreter does not work

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Wouldn't it make more sense to move interpreter initialization things to Py_NewInterpreter and call it from Py_InitializeEx? ___ Python tracker <[EMAIL PROTECTED]>

[issue3723] Py_NewInterpreter does not work

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I think the patch goes in the right direction. But in addition, Py_NewInterpreter() has to call initstdio() between initmain() and initsite() (the same sequence as in Py_InitializeEx) Found by using the following command string in impo

[issue3723] Py_NewInterpreter does not work

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Here is a patch that fixed importexc.c. It consists of the following parts: - set m_size of the builtins module and the sys module to -1, indicating that these modules don't support repeated initialization. This should be reviewed; perhaps it

[issue3723] Py_NewInterpreter does not work

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3723] Py_NewInterpreter does not work

Graham Dumpleton <[EMAIL PROTECTED]> added the comment: Unified diff now attached. Added file: http://bugs.python.org/file11661/pythonrun.c.diff ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3723] Py_NewInterpreter does not work

Changes by Graham Dumpleton <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11660/pythonrun.c.diff ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3723] Py_NewInterpreter does not work

Graham Dumpleton <[EMAIL PROTECTED]> added the comment: Argh. Personally I like to provide context diff's but more often than not get abused for providing them over a unified diff. Was in a hurry this time as had only a couple of minutes of battery life left on the laptop, so quickly did it wi

[issue3723] Py_NewInterpreter does not work

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Your patch may go in the right direction, but please provide only context diff or unified diff files. Use "diff -du", or "svn diff" to generate the file. ___ Python tracker <[EMAIL PROTECTED]>

[issue3723] Py_NewInterpreter does not work

Graham Dumpleton <[EMAIL PROTECTED]> added the comment: Adding the functions as initfunc in module init table is of no use as they aren't invoked when creating a sub interpreter. One thing that does appear to work, although no idea of whether it is correct way to solve problem, is to duplicate

[issue3723] Py_NewInterpreter does not work

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3723] Py_NewInterpreter does not work

Changes by djc <[EMAIL PROTECTED]>: -- nosy: +djc ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing list Unsubscri

[issue3723] Py_NewInterpreter does not work

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Interesting, here it lets import.c's init_builtin reinitalize modules... ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3723] Py_NewInterpreter does not work

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I applied the patch to PC/config.c, but this did not change anything. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3723] Py_NewInterpreter does not work

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- keywords: +needs review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-

[issue3723] Py_NewInterpreter does not work

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Maybe, I'm not seeing the whole problem, but can't we just add _PySys_Init and _PyBuiltin_Init to config.c like in the attached patch? Obviously, we will eventually want to make a separate state to store module globals in, but I think this

[issue3723] Py_NewInterpreter does not work

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3723] Py_NewInterpreter does not work

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3723] Py_NewInterpreter does not work

New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: The example Demo/embed/importexc.c crashes, because Py_NewInterpreter cannot reimport builtins and sys modules. This problem seems important for embedding applications like mod_python, for example. (the "import exceptions" statement d