On Apr 13, 5:20 pm, "durumdara" <[EMAIL PROTECTED]> wrote: > Hi ! > > I want to substitute my modpy based website to any framework system, > but I have a question: > > The development under modpy sometimes became very hard, because the > python in the normal working mode does not reload the modules are > loaded before. > > But in web development when we change something in source, the site > need to reflect these changes. > This is not too easy to solve the problems caused by changes (objects > are changed, some globals are flushed, persistent databases closed, > etc.). > > The developer sometimes is see only the he/she is refreshed the page, > but nothing is happened. Reload problem occured. > > In php that is no problem, because the source is read and interpreted > again by the interpreter, so the changed are reflected in a moment. > > Before of modpy 3.3 I used my own system to load and reinterpret pages > (see exec) without this "reload hell".
In mod_python 3.3.1 do you use mod_python's own module importer? The module importer was completely rewritten for that release and as long as you are disciplined and use it properly, you can go a long way without needing to restart Apache. > I want to ask that how to django avoid these problems when I use > modpython gateway? > Or I need to restart my website after modifications? Django doesn't avoid these problems. You have no choice when using Django on top of mod_python but to restart Apache to have it properly pick up changes as it uses the standard Python module importer. 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?hl=en -~----------~----~----~----~------~----~------~--~---
