#4380: Rename DEFAULT_CHARSET to OUTPUT_CHARSET (or similar) ---------------------------+------------------------------------------------ Reporter: Simon Willison | Owner: adrian Status: new | Component: Core framework Version: other branch | Keywords: Stage: Unreviewed | Has_patch: 0 ---------------------------+------------------------------------------------ Just spotted this in the new unicode documentation (from the unicode branch): Do not be fooled into thinking that if you ``DEFAULT_CHARSET`` setting is set to something other than ``utf-8`` you can use that encoding in your bytestrings! The ``DEFAULT_CHARSET`` only applies to the strings generated as the result of template rendering (and email). Django will always assume UTF-8 encoding for internal bytestrings. The reason for this is that the ``DEFAULT_CHARSET`` setting is not actually under your control (if you are the application developer). It is under the control of the person installing and using your application and if they choose a different setting, your code must still continue to work. Ergo, it cannot rely on that setting. http://code.djangoproject.com/browser/django/branches/unicode/docs/unicode.txt?rev=5330#L57 How about renaming that setting to something more clear, like OUTPUT_CHARSET or DEFAULT_OUTPUT_CHARSET?
-- Ticket URL: <http://code.djangoproject.com/ticket/4380> Django Code <http://code.djangoproject.com/> The web framework for perfectionists with deadlines --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
