On 8/28/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > if there are syntax errors, the file will not compile and the only > error apache will give is incomplete script headers or something like > that. So before running with apache, make sure the file compiles (F5 > in idle). Even if it does compile, if some import errors are there, > again you will not get the error - just the script headers thing
There are lots and lots of potential runtime errors that wouldn't be caught. Just running your stuff in IDLE is not enough. > > > > Save Apache for final deployment. > > no harm in using it for development - that way both devel and > production are on identical platforms I certainly wasn't advocating doing ALL your development *and* testing with the Django server, and then switching to Apache for production. My recommendation is to do all your main development with the Django server. When you're completely happy with how it runs, start testing with Apache. When you're happy with how that runs, switch to production. Jay P. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
