[mod_python] PyThreadState_Delete: tstate is still current

Peter Sanchez petersanchez at gmail.com
Sat Oct 15 00:34:12 EDT 2005

That did it! I only had 1 instance of python installed, but I believe
it was the changes to cache.py that did the trick. No more errors and
it seems to be behaving just fine now!

I *really* appreciate all the effors you and Gregory put into this issue.

Thanks again!


On 10/14/05, Graham Dumpleton <grahamd at dscpl.com.au> wrote:
> On 15/10/2005, at 12:58 PM, Graham Dumpleton wrote:
> > Python's rules for determining the default PYTHON_PATH are stupid.
> >
> > Even when loaded from inside of Apache as part of mod_python, it seems
> > to search PATH for a "python" executable. If it finds one it will
> > assume
> > that that is the correct one and somehow base the PYTHON_PATH on that.
> >
> > I eliminated the "init" problem by simply ensuring that the version of
> > Python I used to build mod_python was the first found in my path. As it
> > was it was still finding the system default version of Python which
> > had mod_python 3.1.4 installed. It therefore was loading mod_python
> > modules from 3.1.4 and not 3.2.2 as installed in my separate copy of
> > Python.
> Should clarify that I am talking about the PATH in the environment when
> Apache is being started/restarted. Ie., I was stopping/starting Apache
> on the command line. Thus it was my personal user PATH environment which
> was inherited by the "apachectl" program that was the problem.
> This issue may explain away some prior cases where people were having
> lots of problems getting mod_python to pick up the correct installed
> Python
> code files for mod_python. :-(
> Graham

More information about the Mod_python mailing list