On Wed, May 5, 2010 at 12:46 PM, Kevin Howerton <kevin.hower...@gmail.com>wrote:
> What I was suggesting in my post though, was that we alter the default > CRITICAL error handling behavior ... as it stands (by default) all of > my ERRORs are being suppressed in production. This is pretty > confusing for new users (there were 3 others in IRC with the same > complaint yesterday), and pretty un-pythonic IMO. Unless I missed > something? > I think you are missing something. From your earlier note you seem to be saying that it is information your own code is writing to stderr that is getting lost somewhere. Django does nothing to suppress anything sent do stderr. I've got views that write to stderr running under mod_wsgi, and the stderr output appears in the configured Apache error log. You do need to either include a newline in the data or explicitly flush stderr for the data to be written, and that may be a difference from mod_python (I don't remember enough about mod_python to say one way or the other). I think the problem you are having is more related to mod_wsgi, and possible differences between it and mod_python, than Django. > At minimum the documentation should inform the user of this > short-coming, and provide a link to a wiki with the available > work-arounds. > It isn't clear to me what shortcoming you think should be documented. If it is the behavior of mod_wsgi with respect to stderr possibly the deployment docs for mod_wsgi could mention something, but one danger of Django putting information like this in the docs is that it gets out of date as mod_wsgi evolves. In general it seems better to provide a minimum amount of information in Django doc, stuff that is specific to Django, and point the user to the appropriate source for authoritative documentation on the 3rd-party package. For the record, Django's default handling of critical errors when DEBUG is False is fully documented: http://docs.djangoproject.com/en/dev/howto/error-reporting/ Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
