Frank Stüss wrote: > Thanks again for anticipation. > > The strange thing is: Apache *has* been restarted (as of message of my > provider). That's why i talked about a cache or something. I found others > experiencing this problem, too. We will see.
If you are using a service provider, ask them whether they have setup the mod_python configuration such that your Django instance is isolated from any other mod_python based or Django based application instance. This is mentioned in the Django installation notes for mod_python at: http://www.djangoproject.com/documentation/modpython/ Specifically, ensure that the "PythonInterpreter" directive is set to a unique name for your area of the URL namespace. If this isn't done, then another web application could be interfering with yours. > I totally agree that a special module reloading mechanism doesn't belong into > django code and i shurely can live with this (if the problem mentioned is > solved). If ever, it must be a middleware something which is totally > transparent to mod_python and django. A module loading mechanism which supports reloading can't be middleware as it needs to be intimately aware of the context it is used. This is because you can't apply reloading to all modules, one can only do it for a selected subset of modules. In mod_python this is those modules which make up the web application. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
