Commits

cca...@bcc190cf-cafb-0310-a4f2-bffc1f526a37  committed 9d75322

[soc2009/http-wsgi-improvements] Fixes for HttpResponse.charsets docs and HttpResponse._charset. Refs #10190.

  • Participants
  • Parent commits 1d55ce8
  • Branches soc2009/http-wsgi-improvements

Comments (0)

Files changed (2)

File django/http/__init__.py

                  content_type=None, request=None):
         from django.conf import settings
         accept_charset = None
-        _charset = settings.DEFAULT_CHARSET
+        self._charset = settings.DEFAULT_CHARSET
         if mimetype:
             content_type = mimetype  # Mimetype arg is an alias for content-type
         if request:
         HttpResponse.__init__(self)
         self['Allow'] = ', '.join(permitted_methods)
 
-class HttpResponseNotAcceptable(HttpResponse):
-    _status_code = 406
-
-    # http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
-    # if we want to make this more verbose (compliant, actually)
-
 class HttpResponseGone(HttpResponse):
     _status_code = 410
 

File django/http/charsets.py

     http://www.iana.org/assignments/character-sets contains valid aliases.
     The documentation for the codecs module has the list of codecs.
     
-    CODEC_CHARSETS above has the codecs that correspond to character sets.
+    _CHARSET_CODECS above has the codecs that correspond to character sets.
     """
     codec = None
     if charset:
     # code in the HttpResponse.
     return charset, codec
 
-# NOTE -- make sure we are not duping the processing of q values
 def _process_accept_charset(accept_charset):
     '''
     HTTP RFC 2616 section 14.2 dictates that q must be between 0 and 1.