Bak @ kedai writes:
no dice. i got the python rpm source, and rebuilt it with --without-pymalloc and zope still restarts. i also tried the rpm binaries from python.org Apparently, there are various SIGSEGV issues with Zope 2.4 and/or Python2.1:
* the "pymalloc" issue * a change in "borrowed/owned" policy with respect to a specific Python function (--> mailing list archives) * a missing "Py_INCREF" in the new "cAccessControl" implementation (--> "zope-dev@zope.org" posts from yesterday and today). Maybe, there are even more issues...
fyi, i have both python versions installed. i just removed /usr/bin/python and symlink /usr/bin/python2 to /usr/bin/python. will this cause problems? i am not too sure myself. Maybe, your Zope did not use "/usr/bin/python" at all!
If your "/usr/bin/python" has been Python 1.5.2 and your Zope was 2.4, then Zope still uses the old Python (not recompiled) which is not located in "/usr/bin". Look at Zope's start script. You should see there, what Python is used. Dieter