Whoops. Looking at code now in Django, it doesn't actually import the Python bindings for Subversion.
What the version module does do though is import minidom which means that pyexpat module is being imported. Thus you may be hitting the following issue: http://www.dscpl.com.au/wiki/ModPython/Articles/ExpatCausingApacheCrash Graham On Nov 13, 4:43 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Nov 13, 3:04 pm, Chase <[EMAIL PROTECTED]> wrote: > > > > > Folks, > > > I've been running 0.96 on my development box with no troubles for the > > past few months, but when I upgraded to the development version last > > week,mod_pythonstarted throwing segmentation faults. I tracked the > > issue to what appears to be the django/__init__.py file in Changeset > > 5990. > > > The changeset only appears to add the Subversion revision number to > > the Django version string. I'm having a hard time understanding how it > > could tweak out mymod_pythonlike that. All I know is that if I pull > > down version 5989 of django/__init__.py, everything works fine. > > > Does anyone know what might be up? Here's my setup: > > > Linux: CentOS 4.4 > > Python: 2.5 > > Apache: 2.0.59Mod_python: 3.2 > > Postgres: 8.1.8 > > > The predictable Apache error_log: > > > [Thu Nov 08 11:43:42 2007] [notice]mod_python: (Re)importing module ' > > django.core.handlers.modpython' > > [Thu Nov 08 11:43:43 2007] [notice] child pid 24474 exit signal > > Segmentation fault (11) > > > Apache conf snippet: > > > <VirtualHost 123.45.678.90> > > DocumentRoot "/home/user/www/" > > ServerName 123.45.678.90 > > ProxyRequests Off > > ProxyPreserveHost On > > ProxyPass /site/media/ http:// 123.45.678.90:81/ > > ProxyPassReverse / http:// 123.45.678.90:81/ > > <Location "/site"> > > SetHandler python-program > > PythonHandler django.core.handlers.modpython > > SetEnv DJANGO_SETTINGS_MODULE site.settings > > PythonDebug On > > PythonPath "['/home/user/django_projects'] + sys.path" > > </Location> > > ETC ... > > </VirtualHost> > > > I'll submit a ticket, but I want to be sure I'm not overlooking > > something stupid first ... > > If Django is importing subversion, then mod_python must be forced to > run in the main Python interpreter by setting mod_python directive: > > PythonInterpreter main_interpreter > > This is a known problem with Python bindings for subversion,. ie., > that they don't work reliably if not run in first interpreter created > by Python. > > I hope that this importing of subversion by Django is optional and > only used if necessary, else this will prevent multiple Django sites > running under mod_python if subversion is installed, given that the > only way of running multiple Django sites now is to run them in > separate Python sub interpreters when using mod_python. > > Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
