I found a workaround...
Setting WSGIApplicationGroup = ${GLOBAL}
for each app and adding a patch to sqlalchemy.databases.firebird.py to
check self.dbapi.initialization before calling self.dbapi.init()
This causes all the apps to run under one python subinterpreter and
the global variable in kinter
Sorry for not explaining myself more clearly, but the global
initialized variable in the kinterbasdb module being set to true
(which it should be once initialized) is check first thing when the
init method is called.
This is supposed to throw a specific programming error.
relevant code from kinte
On Sep 30, 2008, at 2:46 PM, Michael Shaw wrote:
>
> I am working on two projects that are bothing running under mod_wsgi.
> The first is using kinterbasdb directly (no sqlalchemy).
> The second is using sqlalchemy.
> Problem arises when one or the other attempts to call kinterbasdb.init
> after
