id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 9430,Writing Views makes reference to previously mentioned issue but doesn't say where,Chris Lyon,nobody,"http://docs.djangoproject.com/en/dev/topics/http/views/ to quote: Returning HTTP error codes in Django is easy. We've already mentioned the HttpResponseNotFound, HttpResponseForbidden, HttpResponseServerError, etc., subclasses; just return an instance of one of those subclasses instead of a normal HttpResponse in order to signify an error. For example: It says we've already mentioned but it would be useful if their were a pointer to where these errors are first mentioned. I came at this from a methodical reading of the view documentation and felt that their should have been some indication as to where these objects were first introduced. ",,closed,Documentation,1.0,,fixed,,,Unreviewed,0,0,0,0,0,0