On Jul 30, 12:33 am, nimrod <nsteinb...@gmail.com
> I compiled the new version ofmod_wsgi, configured it, and it works!
> I guessmod_wsgiis going to replace mod_python throughout our
> production env
In private email you said it didn't work with mod_wsgi 1.3. I don't
understand why you would have an issue with mod_wsgi 1.3 and not
mod_wsgi 2.1. The code that relates to simplified GIL state API is the
same in both versions.
If you can provide a really simple hello world example independent of
Django that demonstrates original problem that would help me, as could
do some testing of my own.
> Thanks Graham!
> On Jul 29, 3:37 pm, Graham Dumpleton <Graham.Dumple...@gmail.com
> > On Jul 29, 9:59 pm, nimrod <nsteinb...@gmail.com
> > > Hi,
> > > I developed a xappy/xapian based app using django. While running on
> > > the django dev server all is well, but when deploying with apache the
> > > server goes into a deadlock (waiting for localhost...). When I remove
> > > the "import xappy" line from my code it runs just fine.
> > > Looking here:http://trac.xapian.org/ticket/185
> > > It seems that I have to use:
> > > PythonInterpreter main_interpreter
> > > in my apache config file for using xapian. I tried that - no good
> > > Looking some more I saw in the same report:
> > > "Even with main_interpreter and Python >= 2.4, calling from Xapian's C+
> > > + code back to Python code won't work properly Even with
> > > main_interpreter and Python >= 2.4 (this means that you can't subclass
> > > Xapian objects in Python). "
> > > I guess xappy is doing just that (i.e., subclassing xapian classes)
> > > and thus is not usable with mod_python.
> > > Help anyone?
> > On basis that Django works on any WSGI server, as indicated in ticket
> > should work, can you trymod_wsgiinstead. You still need to force use