The dev server operates much differently than an actual production server. The production server will only evaluate module code once when the module is initially loaded. It doesn't automatically scan for file changes and load files as necessary like the dev server does. If you want file changes to be reflected, you need to restart your server (or change some apache settings I think).
This actually works to your advantage if you put your forms in a file that's loaded as a module rather than in say a view function. If you have a forms.py file with your forms they will only be evaluated once when forms.py file is first loaded. so Form = forms_for_model() actually creates form once, and not every request or every time you instantiate a form. This also makes dynamic choices a bit tough to deal with, but that is another issue! You still have form instantiation to be done any time you use the form, but unless you want to give up most of the goodies newforms offers I don't see a way around that. I have a feeling the overhead of form creation is really pretty small compared to other factors. On the other hand, if you need to render the same blank form page to a bunch of requests, you could render the entire page and cache it using one of Django's cache backends and do something similar to what you suggest. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
