This seems to have veered off in a strange direction, the original poster made no mention of debugging in a production environment. He simply asked for something more efficient than print statements.
-+ enlight +- [EMAIL PROTECTED] wrote: > Nothing stops you from running both production mode server and dev. > server same > time. > > If we are talking about debugging Django application itself (not the > production environment > but the application code) then this approach works well, and more then > well. > > With PHP for example,every debug statement I would use on production > server, will > be seen by end users. In django, I easily fire up dev. server, debug > and fix the problem > without getting users annoyed by my debug statements. I beleive all > user should > see in case of internal server error for example is the "Internal > server error" well > designed page. No debug statements. Nothing else. Thats security. > > Alex --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
