Brian Ray wrote: > Graham: > > This behavior has been seen with mod_python under certian instances. > For example how to the settings in httpd.conf effect this? For example, > "PythonAutoReload On" and apache's MaxRequestsPerChild 1. Maybe they > can aggravate a problem when something else is going wrong I am just > saying
Django does not use the mod_python module importer directly and where it is used by the Python*Handler directives, it doesn't come into play as the Django application modules themselves aren't going to be getting modified on the fly. In other words, whether automatic module reloading within the mod_python module importer is enabled or not would make no difference as the neither the Django application modules, or the users own code modules making up his web application should be candidates for reloading via the mod_python module importer. The only possibility for module importer problems since reloading wasn't an issue, is if the person was using a multithreaded MPM and was using a version of mod_python older than 3.2.7. This wasn't the case though as they still saw the problem when they were using 3.2.10. If Django is implementing its own module reloading mechanism for users code modules making up the web application, I wouldn't be surprised you would be having problems as Django relies on using Python packages to hold the web application modules and reloading of parts of a Python package nearly always can't be done without causing lots of problems. As to using MaxRequestsPerChild, if Django is using a separate database for maintaining sessions that also shouldn't be an issue. The only place that would cause an issue would be on Windows and mod_python Sessions were being used with the in memory session database as you would loose all session information across requests. > I can see other places on the mod_python list where sessions > were not working properly for many reasons. The only problem with that assumption as I understand it is that Django doesn't use the mod_python Session mechanism but has implemented its own. Therefore, any issues people have with mod_python Sessions through not using them properly wouldn't be relevant. > I can recall once I build mod_python linking to the wrong libraries, > and some strange stuff happened. Using the wrong libraries can cause problems with any application and isn't something that would be particularly unique to mod_python. :-) Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
