Thanks to you. So it is like it is. No short changes on a virtually hosted production server with mod_python :)
And my second problem doesn't belong in this list. After googling again i found that it may be caused by a wrong compiled mod_python (two mod_python versions with to python versions on the server). Very strange behaviour: every other request apache complains about errors that have been fixed sessions ago like missing templates or the like. The next browser reload is ok and so on. Like mod_python sessions were cached even after restarting apache and some requests got the 'wrong' mod_python instance. Strange. Have fun djangoing, Frank Am Donnerstag, 31. August 2006 02:20 schrieb Graham Dumpleton: > Kenneth Gonsalves wrote: > > On 30-Aug-06, at 3:35 PM, Frank Stüss wrote: > > > on a production server with mod_python, how can i force reloading > > > all .py > > > files without restarting apache? > > > > you cant > > To clarify, this is only the case where the Python code file is loaded > by Django using its own methods for importing modules. > > As far as mod_python itself goes, there are mechanisms for having > code files it loads be reloaded when changed, but Django isn't going > to use that feature of mod_python directly, as that then means there > is an unwanted dependency on mod_python. > > That said, for versions of mod_python < 3.3, the module reloading > ability does have some problems. See: > > http://www.dscpl.com.au/articles/modpython-003.html > > for details. Pretty well all of these issues are addressed in yet to be > released mod_python 3.3 however. > > Now it is probably technically feasible that Django could harness the > improved module reloading abilities in mod_python 3.3 in such a way > that it would be transparent and not cause a dependency in user code > on mod_python, thus allowing you to be able to do what you want, but > I tend to think that you would have a hard time getting such a thing > added into Django. :-) > > 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 -~----------~----~----~----~------~----~------~--~---
