This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author grahamd
Recipients amaury.forgeotdarc, benjamin.peterson, djc, grahamd, loewis
Date 2008-09-30.12:15:28
SpamBayes Score 1.03099e-10
Marked as misclassified No
Message-id <1222776932.9.0.132375046627.issue3723@psf.upfronthosting.co.za>
In-reply-to
Content
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 the builtin/sys 
initialisation that occurs in Py_InitializeEx() function.

Attached diff shows nature of changes. Diff is bit messy as have left 
existing code in there but #ifdef'd out.

Maybe this will give someone who knows how overall interpreter 
initialisation is supposed to work a head start on coming up with proper 
fix. But then it could be totally wrong as well.

At least with change as is, mod_wsgi works for sub interpreters now. 
I'll do more work later on whether it is correct way to solve it.
History
Date User Action Args
2008-09-30 12:15:33grahamdsetrecipients: + grahamd, loewis, amaury.forgeotdarc, benjamin.peterson, djc
2008-09-30 12:15:32grahamdsetmessageid: <1222776932.9.0.132375046627.issue3723@psf.upfronthosting.co.za>
2008-09-30 12:15:30grahamdlinkissue3723 messages
2008-09-30 12:15:29grahamdcreate