Also the 5XX page is necessary IMHO. In general it is not recommended to show too much error information to the user on a production system due to security issues (revealing paths, versions and code). However, I think that a sensible 5XX page with the stacktrace would be a better user experience. The standard plain 500 page leaves users very confused. Showing the stack-trace end the exception will make it more clear that something is not right and we are more likely to get a screenshot with usefull debug information on first contact. But in any case I would limit this to authenticated users.
We should have a nice 4XX page for production.
Also the 5XX page is necessary IMHO. In general it is not recommended to show too much error information to the user on a production system due to security issues (revealing paths, versions and code). However, I think that a sensible 5XX page with the stacktrace would be a better user experience. The standard plain 500 page leaves users very confused. Showing the stack-trace end the exception will make it more clear that something is not right and we are more likely to get a screenshot with usefull debug information on first contact. But in any case I would limit this to authenticated users.
Further information about this can be found in the Django docs: https://docs.djangoproject.com/en/dev/topics/http/views/#customizing-error-views