> 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
Wait, wait.. When the error occurs, message is GENERATED. it should not be consumed, but saved somewhere. Better go apache log... And people here tell me set admin email.. So I will get emails with errors WHILE I DEVELOP on my home box! *rofl* Maybe django redirects stdout/stderr somewhere so the errors get consumed ? > > > Save Apache for final deployment. > > no harm in using it for development - that way both devel and > production are on identical platforms I too can't understand why I shouldn't develop on apache. Usually people recommend use same env for development and production. Less weak points. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
